Power Control for Mobility Handover in a Radio System

ABSTRACT

A wireless device receives one or more messages indicating a handover to a cell of a second base station. The one or more messages comprise configuration parameters of the cell. The configuration parameters indicate a plurality of power control parameter sets (PCPSs). The configuration parameters indicate a plurality of downlink reference signals. A downlink reference signal of the plurality of downlink reference signals is determined based on measurements of the plurality of downlink reference signals. A PCPS is selected from the plurality of PCPSs. The PCPS is associated with the downlink reference signal. An uplink transmission power is determined, based on the PCPS, for a physical uplink shared channel (PUSCH) of the cell. An uplink transport block is transmitted with the uplink transmission power via the PUSCH of the cell.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.62/824,135, filed Mar. 26, 2019, which is hereby incorporated byreference in its entirety.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 2A is a diagram of an example user plane protocol stack as per anaspect of an embodiment of the present disclosure.

FIG. 2B is a diagram of an example control plane protocol stack as peran aspect of an embodiment of the present disclosure.

FIG. 3 is a diagram of an example wireless device and two base stationsas per an aspect of an embodiment of the present disclosure.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals as per an aspect of an embodiment of the presentdisclosure.

FIG. 5B is a diagram of an example downlink channel mapping and exampledownlink physical signals as per an aspect of an embodiment of thepresent disclosure.

FIG. 6 is a diagram depicting an example transmission time or receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure.

FIG. 7A and FIG. 7B are diagrams depicting example sets of OFDMsubcarriers as per an aspect of an embodiment of the present disclosure.

FIG. 8 is a diagram depicting example OFDM radio resources as per anaspect of an embodiment of the present disclosure.

FIG. 9A is a diagram depicting an example CSI-RS and/or SS blocktransmission in a multi-beam system.

FIG. 9B is a diagram depicting an example downlink beam managementprocedure as per an aspect of an embodiment of the present disclosure.

FIG. 10 is an example diagram of configured BWPs as per an aspect of anembodiment of the present disclosure.

FIG. 11A, and FIG. 11B are diagrams of an example multi connectivity asper an aspect of an embodiment of the present disclosure.

FIG. 12 is a diagram of an example random access procedure as per anaspect of an embodiment of the present disclosure.

FIG. 13 is a structure of example MAC entities as per an aspect of anembodiment of the present disclosure.

FIG. 14 is a diagram of an example RAN architecture as per an aspect ofan embodiment of the present disclosure.

FIG. 15 is a diagram of example RRC states as per an aspect of anembodiment of the present disclosure.

FIG. 16 is an example of CSI RS transmission with multiple beams as peran aspect of an embodiment of the present disclosure.

FIG. 17 is an example of various beam management procedures as per anaspect of an embodiment of the present disclosure.

FIG. 18 is an example of DCI formats as per an aspect of an embodimentof the present disclosure.

FIG. 19 is an example of mobility handover procedure as per an aspect ofan embodiment of the present disclosure.

FIG. 20A is an example of physical uplink shared channel (PUSCH)transmission procedure in mobility handover as per an aspect of anembodiment of the present disclosure.

FIG. 20B is an example of PUSCH transmission procedure in mobilityhandover as per an aspect of an embodiment of the present disclosure.

FIG. 21 is an example of power control procedure for PUSCH transmissionas per an aspect of an embodiment of the present disclosure.

FIG. 22 is an example of power control flow chart for PUSCH transmissionas per an aspect of an embodiment of the present disclosure.

FIG. 23A is an example of physical uplink shared channel (PUSCH)transmission procedure in mobility handover as per an aspect of anembodiment of the present disclosure.

FIG. 23B is an example of PUSCH transmission procedure in mobilityhandover as per an aspect of an embodiment of the present disclosure.

FIG. 24 is an example of power control procedure for PUSCH transmissionas per an aspect of an embodiment of the present disclosure.

FIG. 25 is an example of power control flow chart for PUSCH transmissionas per an aspect of an embodiment of the present disclosure.

FIG. 26 is an example of switching procedure for PUSCH transmission inmobility handover as per an aspect of an embodiment of the presentdisclosure.

FIG. 27 is an example of power control procedure for preambletransmission as per an aspect of an embodiment of the presentdisclosure.

FIG. 28 is an example of power control flow chart for preambletransmission as per an aspect of an embodiment of the presentdisclosure.

FIG. 29 is an example of switching procedure for PUSCH transmission inmobility handover as per an aspect of an embodiment of the presentdisclosure.

FIG. 30 is an example of power control procedure for PUSCH transmissionas per an aspect of an embodiment of the present disclosure.

FIG. 31 is an example of power control flow chart for PUSCH transmissionas per an aspect of an embodiment of the present disclosure.

FIG. 32 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

FIG. 33 is a flow diagram of an aspect of an example embodiment of thepresent disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

Example embodiments of the present disclosure enable power controloperations with mobility handover of a wireless device and/or a basestation. Embodiments of the technology disclosed herein may be employedin the technical field of power control and mobility handover formultiple cells and low interruption communication systems. Moreparticularly, the embodiments of the technology disclosed herein mayrelate to a wireless device and/or a base station in a multiple cellsand low interruption communication system with high speed mobility andefficient power control.

The following Acronyms are used throughout the present disclosure:

3GPP 3rd Generation Partnership Project 5GC 5G Core Network ACKAcknowledgement AMF Access and Mobility Management Function ARQAutomatic Repeat Request AS Access Stratum ASIC Application-SpecificIntegrated Circuit BA Bandwidth Adaptation BCCH Broadcast ControlChannel BCH Broadcast Channel BPSK Binary Phase Shift Keying BWPBandwidth Part CA Carrier Aggregation CC Component Carrier CCCH CommonControl CHannel CDMA Code Division Multiple Access CN Core Network CPCyclic Prefix CP-OFDM Cyclic Prefix- Orthogonal Frequency DivisionMultiplex C-RNTI Cell-Radio Network Temporary Identifier CS ConfiguredScheduling CSI Channel State Information CSI-RS Channel StateInformation-Reference Signal CQI Channel Quality Indicator CSS CommonSearch Space CU Central Unit DAI Downlink Assignment Index DC DualConnectivity DCCH Dedicated Control Channel DCI Downlink ControlInformation DL Downlink DL-SCH Downlink Shared CHannel DM-RSDeModulation Reference Signal DRB Data Radio Bearer DRX DiscontinuousReception DTCH Dedicated Traffic Channel DU Distributed Unit EPC EvolvedPacket Core E-UTRA Evolved UMTS Terrestrial Radio Access E-UTRANEvolved-Universal Terrestrial Radio Access Network FDD FrequencyDivision Duplex FPGA Field Programmable Gate Arrays F1-C F1-Controlplane F1-U F1-User plane gNB next generation Node B HARQ HybridAutomatic Repeat reQuest HDL Hardware Description Languages IEInformation Element IP Internet Protocol LCID Logical Channel IdentifierLTE Long Term Evolution MAC Media Access Control MCG Master Cell GroupMCS Modulation and Coding Scheme MeNB Master evolved Node B MIB MasterInformation Block MME Mobility Management Entity MN Master Node NACKNegative Acknowledgement NAS Non-Access Stratum NG CP Next GenerationControl Plane NGC Next Generation Core NG-C NG-Control plane ng-eNB nextgeneration evolved Node B NG-U NG-User plane NR New Radio NR MAC NewRadio MAC NR PDCP New Radio PDCP NR PHY New Radio PHYsical NR RLC NewRadio RLC NR RRC New Radio RRC NSSAI Network Slice Selection AssistanceInformation O&M Operation and Maintenance OFDM orthogonal FrequencyDivision Multiplexing PBCH Physical Broadcast CHannel PCC PrimaryComponent Carrier PCCH Paging Control CHannel PCell Primary Cell PCHPaging CHannel PDCCH Physical Downlink Control CHannel PDCP Packet DataConvergence Protocol PDSCH Physical Downlink Shared CHannel PDU ProtocolData Unit PHICH Physical HARQ Indicator CHannel PHY PHYsical PLMN PublicLand Mobile Network PMI Precoding Matrix Indicator PRACH Physical RandomAccess CHannel PRB Physical Resource Block PSCell Primary Secondary CellPSS Primary Synchronization Signal pTAG primary Timing Advance GroupPT-RS Phase Tracking Reference Signal PUCCH Physical Uplink ControlCHannel PUSCH Physical Uplink Shared CHannel QAM Quadrature AmplitudeModulation QFI Quality of Service Indicator QoS Quality of Service QPSKQuadrature Phase Shift Keying RA Random Access RACH Random AccessCHannel RAN Radio Access Network RAT Radio Access Technology RA-RNTIRandom Access-Radio Network Temporary Identifier RB Resource Blocks RBGResource Block Groups RI Rank indicator RLC Radio Link Control RLM RadioLink Monitoring RNTI Radio Network Temporary Identifier RRC RadioResource Control RRM Radio Resource Management RS Reference Signal RSRPReference Signal Received Power SCC Secondary Component Carrier SCellSecondary Cell SCG Secondary Cell Group SC-FDMA Single Carrier-FrequencyDivision Multiple Access SDAP Service Data Adaptation Protocol SDUService Data Unit SeNB Secondary evolved Node B SFN System Frame NumberS-GW Serving GateWay SI System Information SIB System Information BlockSMF Session Management Function SN Secondary Node SpCell Special CellSRB Signaling Radio Bearer SRS Sounding Reference Signal SSSynchronization Signal SSS Secondary Synchronization Signal sTAGsecondary Timing Advance Group TA Timing Advance TAG Timing AdvanceGroup TAI Tracking Area Identifier TAT Time Alignment Timer TB TransportBlock TCI Transmission Configuration Indication TC-RNTI TemporaryCell-Radio Network Temporary Identifier TDD Time Division Duplex TDMATime Division Multiple Access TRP Transmission Reception Point TTITransmission Time Interval UCI Uplink Control Information UE UserEquipment UL Uplink UL-SCH Uplink Shared CHannel UPF User Plane FunctionUPGW User Plane Gateway VHDL VHSIC Hardware Description Language Xn-CXn-Control plane Xn-U Xn-User plane

Example embodiments of the disclosure may be implemented using variousphysical layer modulation and transmission mechanisms. Exampletransmission mechanisms may include, but not limited to: Code DivisionMultiple Access (CDMA), Orthogonal Frequency Division Multiple Access(OFDMA), Time Division Multiple Access (TDMA), Wavelet technologies,and/or the like. Hybrid transmission mechanisms such as TDMA/CDMA, andOFDM/CDMA may also be employed. Various modulation schemes may beapplied for signal transmission in the physical layer. Examples ofmodulation schemes include, but are not limited to: phase, amplitude,code, a combination of these, and/or the like. An example radiotransmission method may implement Quadrature Amplitude Modulation (QAM)using Binary Phase Shift Keying (BPSK), Quadrature Phase Shift Keying(QPSK), 16-QAM, 64-QAM, 256-QAM, 1024-QAM, and/or the like. Physicalradio transmission may be enhanced by dynamically or semi-dynamicallychanging the modulation and coding scheme depending on transmissionrequirements and radio conditions.

FIG. 1 is an example Radio Access Network (RAN) architecture as per anaspect of an embodiment of the present disclosure. As illustrated inthis example, a RAN node may be a next generation Node B (gNB) (e.g.120A, 120B) providing New Radio (NR) user plane and control planeprotocol terminations towards a first wireless device (e.g. 110A). In anexample, a RAN node may be a next generation evolved Node B (ng-eNB)(e.g. 120C, 120D), providing Evolved UMTS Terrestrial Radio Access(E-UTRA) user plane and control plane protocol terminations towards asecond wireless device (e.g. 110B). The first wireless device maycommunicate with a gNB over a Uu interface. The second wireless devicemay communicate with a ng-eNB over a Uu interface.

A gNB or an ng-eNB may host functions such as radio resource managementand scheduling, IP header compression, encryption and integrityprotection of data, selection of Access and Mobility Management Function(AMF) at User Equipment (UE) attachment, routing of user plane andcontrol plane data, connection setup and release, scheduling andtransmission of paging messages (originated from the AMF), schedulingand transmission of system broadcast information (originated from theAMF or Operation and Maintenance (O&M)), measurement and measurementreporting configuration, transport level packet marking in the uplink,session management, support of network slicing, Quality of Service (QoS)flow management and mapping to data radio bearers, support of UEs inRRC_INACTIVE state, distribution function for Non-Access Stratum (NAS)messages, RAN sharing, dual connectivity or tight interworking betweenNR and E-UTRA.

In an example, one or more gNBs and/or one or more ng-eNBs may beinterconnected with each other by means of Xn interface. A gNB or anng-eNB may be connected by means of NG interfaces to 5G Core Network(5GC). In an example, 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g. 130A or 130B). A gNB or an ng-eNB may beconnected to a UPF by means of an NG-User plane (NG-U) interface. TheNG-U interface may provide delivery (e.g. non-guaranteed delivery) ofuser plane Protocol Data Units (PDUs) between a RAN node and the UPF. AgNB or an ng-eNB may be connected to an AMF by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide functions such asNG interface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, configurationtransfer or warning message transmission.

In an example, a UPF may host functions such as anchor point forintra-/inter-Radio Access Technology (RAT) mobility (when applicable),external PDU session point of interconnect to data network, packetrouting and forwarding, packet inspection and user plane part of policyrule enforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, QoS handling for user plane, e.g. packetfiltering, gating, Uplink (UL)/Downlink (DL) rate enforcement, uplinktraffic verification (e.g. Service Data Flow (SDF) to QoS flow mapping),downlink packet buffering and/or downlink data notification triggering.

In an example, an AMF may host functions such as NAS signalingtermination, NAS signaling security, Access Stratum (AS) securitycontrol, inter Core Network (CN) node signaling for mobility between3^(rd) Generation Partnership Project (3GPP) access networks, idle modeUE reachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (subscription and policies),support of network slicing and/or Session Management Function (SMF)selection.

FIG. 2A is an example user plane protocol stack, where Service DataAdaptation Protocol (SDAP) (e.g. 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g. 212 and 222), Radio Link Control (RLC) (e.g. 213and 223) and Media Access Control (MAC) (e.g. 214 and 224) sublayers andPhysical (PHY) (e.g. 215 and 225) layer may be terminated in wirelessdevice (e.g. 110) and gNB (e.g. 120) on the network side. In an example,a PHY layer provides transport services to higher layers (e.g. MAC, RRC,etc.). In an example, services and functions of a MAC sublayer maycomprise mapping between logical channels and transport channels,multiplexing/demultiplexing of MAC Service Data Units (SDUs) belongingto one or different logical channels into/from Transport Blocks (TB s)delivered to/from the PHY layer, scheduling information reporting, errorcorrection through Hybrid Automatic Repeat request (HARQ) (e.g. one HARQentity per carrier in case of Carrier Aggregation (CA)), priorityhandling between UEs by means of dynamic scheduling, priority handlingbetween logical channels of one UE by means of logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. In an example, mappingrestrictions in a logical channel prioritization may control whichnumerology and/or transmission timing a logical channel may use. In anexample, an RLC sublayer may supports transparent mode (TM),unacknowledged mode (UM) and acknowledged mode (AM) transmission modes.The RLC configuration may be per logical channel with no dependency onnumerologies and/or Transmission Time Interval (TTI) durations. In anexample, Automatic Repeat Request (ARQ) may operate on any of thenumerologies and/or TTI durations the logical channel is configuredwith. In an example, services and functions of the PDCP layer for theuser plane may comprise sequence numbering, header compression anddecompression, transfer of user data, reordering and duplicatedetection, PDCP PDU routing (e.g. in case of split bearers),retransmission of PDCP SDUs, ciphering, deciphering and integrityprotection, PDCP SDU discard, PDCP re-establishment and data recoveryfor RLC AM, and/or duplication of PDCP PDUs. In an example, services andfunctions of SDAP may comprise mapping between a QoS flow and a dataradio bearer. In an example, services and functions of SDAP may comprisemapping Quality of Service Indicator (QFI) in DL and UL packets. In anexample, a protocol entity of SDAP may be configured for an individualPDU session.

FIG. 2B is an example control plane protocol stack where PDCP (e.g. 233and 242), RLC (e.g. 234 and 243) and MAC (e.g. 235 and 244) sublayersand PHY (e.g. 236 and 245) layer may be terminated in wireless device(e.g. 110) and gNB (e.g. 120) on a network side and perform service andfunctions described above. In an example, RRC (e.g. 232 and 241) may beterminated in a wireless device and a gNB on a network side. In anexample, services and functions of RRC may comprise broadcast of systeminformation related to AS and NAS, paging initiated by 5GC or RAN,establishment, maintenance and release of an RRC connection between theUE and RAN, security functions including key management, establishment,configuration, maintenance and release of Signaling Radio Bearers (SRBs)and Data Radio Bearers (DRBs), mobility functions, QoS managementfunctions, UE measurement reporting and control of the reporting,detection of and recovery from radio link failure, and/or NAS messagetransfer to/from NAS from/to a UE. In an example, NAS control protocol(e.g. 231 and 251) may be terminated in the wireless device and AMF(e.g. 130) on a network side and may perform functions such asauthentication, mobility management between a UE and a AMF for 3GPPaccess and non-3GPP access, and session management between a UE and aSMF for 3GPP access and non-3GPP access.

In an example, a base station may configure a plurality of logicalchannels for a wireless device. A logical channel in the plurality oflogical channels may correspond to a radio bearer and the radio bearermay be associated with a QoS requirement. In an example, a base stationmay configure a logical channel to be mapped to one or moreTTIs/numerologies in a plurality of TTIs/numerologies. The wirelessdevice may receive a Downlink Control Information (DCI) via PhysicalDownlink Control CHannel (PDCCH) indicating an uplink grant. In anexample, the uplink grant may be for a first TTI/numerology and mayindicate uplink resources for transmission of a transport block. Thebase station may configure each logical channel in the plurality oflogical channels with one or more parameters to be used by a logicalchannel prioritization procedure at the MAC layer of the wirelessdevice. The one or more parameters may comprise priority, prioritizedbit rate, etc. A logical channel in the plurality of logical channelsmay correspond to one or more buffers comprising data associated withthe logical channel. The logical channel prioritization procedure mayallocate the uplink resources to one or more first logical channels inthe plurality of logical channels and/or one or more MAC ControlElements (CEs). The one or more first logical channels may be mapped tothe first TTI/numerology. The MAC layer at the wireless device maymultiplex one or more MAC CEs and/or one or more MAC SDUs (e.g., logicalchannel) in a MAC PDU (e.g., transport block). In an example, the MACPDU may comprise a MAC header comprising a plurality of MAC sub-headers.A MAC sub-header in the plurality of MAC sub-headers may correspond to aMAC CE or a MAC SUD (logical channel) in the one or more MAC CEs and/orone or more MAC SDUs. In an example, a MAC CE or a logical channel maybe configured with a Logical Channel IDentifier (LCID). In an example,LCID for a logical channel or a MAC CE may be fixed/pre-configured. Inan example, LCID for a logical channel or MAC CE may be configured forthe wireless device by the base station. The MAC sub-headercorresponding to a MAC CE or a MAC SDU may comprise LCID associated withthe MAC CE or the MAC SDU.

In an example, a base station may activate and/or deactivate and/orimpact one or more processes (e.g., set values of one or more parametersof the one or more processes or start and/or stop one or more timers ofthe one or more processes) at the wireless device by employing one ormore MAC commands. The one or more MAC commands may comprise one or moreMAC control elements. In an example, the one or more processes maycomprise activation and/or deactivation of PDCP packet duplication forone or more radio bearers. The base station may transmit a MAC CEcomprising one or more fields, the values of the fields indicatingactivation and/or deactivation of PDCP duplication for the one or moreradio bearers. In an example, the one or more processes may compriseChannel State Information (CSI) transmission of on one or more cells.The base station may transmit one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells. Inan example, the one or more processes may comprise activation ordeactivation of one or more secondary cells. In an example, the basestation may transmit a MA CE indicating activation or deactivation ofone or more secondary cells. In an example, the base station maytransmit one or more MAC CEs indicating starting and/or stopping one ormore Discontinuous Reception (DRX) timers at the wireless device. In anexample, the base station may transmit one or more MAC CEs indicatingone or more timing advance values for one or more Timing Advance Groups(TAGs).

FIG. 3 is a block diagram of base stations (base station 1, 120A, andbase station 2, 120B) and a wireless device 110. A wireless device maybe called an UE. A base station may be called a NB, eNB, gNB, and/orng-eNB. In an example, a wireless device and/or a base station may actas a relay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g. a wireless modem, an antenna, a wiredmodem, and/or the like), at least one processor 321A, and at least oneset of program code instructions 323A stored in non-transitory memory322A and executable by the at least one processor 321A. The base station2, 120B, may comprise at least one communication interface 320B, atleast one processor 321B, and at least one set of program codeinstructions 323B stored in non-transitory memory 322B and executable bythe at least one processor 321B.

A base station may comprise many sectors for example: 1, 2, 3, 4, or 6sectors. A base station may comprise many cells, for example, rangingfrom 1 to 50 cells or more. A cell may be categorized, for example, as aprimary cell or secondary cell. At Radio Resource Control (RRC)connection establishment/re-establishment/handover, one serving cell mayprovide the NAS (non-access stratum) mobility information (e.g. TrackingArea Identifier (TAI)). At RRC connection re-establishment/handover, oneserving cell may provide the security input. This cell may be referredto as the Primary Cell (PCell). In the downlink, a carrier correspondingto the PCell may be a DL Primary Component Carrier (PCC), while in theuplink, a carrier may be an UL PCC. Depending on wireless devicecapabilities, Secondary Cells (SCells) may be configured to formtogether with a PCell a set of serving cells. In a downlink, a carriercorresponding to an SCell may be a downlink secondary component carrier(DL SCC), while in an uplink, a carrier may be an uplink secondarycomponent carrier (UL SCC). An SCell may or may not have an uplinkcarrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and a cell index. A carrier (downlinkor uplink) may belong to one cell. The cell ID or cell index may alsoidentify the downlink carrier or uplink carrier of the cell (dependingon the context it is used). In the disclosure, a cell ID may be equallyreferred to a carrier ID, and a cell index may be referred to a carrierindex. In an implementation, a physical cell ID or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted on a downlink carrier. A cell index may be determinedusing RRC messages. For example, when the disclosure refers to a firstphysical cell ID for a first downlink carrier, the disclosure may meanthe first physical cell ID is for a cell comprising the first downlinkcarrier. The same concept may apply to, for example, carrier activation.When the disclosure indicates that a first carrier is activated, thespecification may equally mean that a cell comprising the first carrieris activated.

A base station may transmit to a wireless device one or more messages(e.g. RRC messages) comprising a plurality of configuration parametersfor one or more cells. One or more cells may comprise at least oneprimary cell and at least one secondary cell. In an example, an RRCmessage may be broadcasted or unicasted to the wireless device. In anexample, configuration parameters may comprise common parameters anddedicated parameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and NAS; paginginitiated by 5GC and/or NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and NG-RAN, whichmay comprise at least one of addition, modification and release ofcarrier aggregation; or addition, modification, and/or release of dualconnectivity in NR or between E-UTRA and NR. Services and/or functionsof an RRC sublayer may further comprise at least one of securityfunctions comprising key management; establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and/orData Radio Bearers (DRBs); mobility functions which may comprise atleast one of a handover (e.g. intra NR mobility or inter-RAT mobility)and a context transfer; or a wireless device cell selection andreselection and control of cell selection and reselection. Servicesand/or functions of an RRC sublayer may further comprise at least one ofQoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; or NAS message transfer to/from a core network entity (e.g.AMF, Mobility Management Entity (MME)) from/to the wireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive stateand/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection/re-selection; monitoring/receiving a paging for mobileterminated data initiated by 5GC; paging for mobile terminated data areamanaged by 5GC; or DRX for CN paging configured via NAS. In anRRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection/re-selection;monitoring/receiving a RAN/CN paging initiated by NG-RAN/5GC; RAN-basednotification area (RNA) managed by NG-RAN; or DRX for RAN/CN pagingconfigured by NG-RAN/NAS. In an RRC_Idle state of a wireless device, abase station (e.g. NG-RAN) may keep a 5GC-NG-RAN connection (bothC/U-planes) for the wireless device; and/or store a UE AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g. NG-RAN) may perform at least one of: establishment of5GC-NG-RAN connection (both C/U-planes) for the wireless device; storinga UE AS context for the wireless device; transmit/receive of unicastdata to/from the wireless device; or network-controlled mobility basedon measurement results received from the wireless device. In anRRC_Connected state of a wireless device, an NG-RAN may know a cell thatthe wireless device belongs to.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and information foracquiring any other SI broadcast periodically or provisioned on-demand,i.e. scheduling information. The other SI may either be broadcast, or beprovisioned in a dedicated manner, either triggered by a network or uponrequest from a wireless device. A minimum SI may be transmitted via twodifferent downlink channels using different messages (e.g.MasterInformationBlock and SystemInformationBlockType1). Another SI maybe transmitted via SystemInformationBlockType2. For a wireless device inan RRC_Connected state, dedicated RRC signaling may be employed for therequest and delivery of the other SI. For the wireless device in theRRC_Idle state and/or the RRC_Inactive state, the request may trigger arandom-access procedure.

A wireless device may report its radio access capability informationwhich may be static. A base station may request what capabilities for awireless device to report based on band information. When allowed by anetwork, a temporary capability restriction request may be sent by thewireless device to signal the limited availability of some capabilities(e.g. due to hardware sharing, interference or overheating) to the basestation. The base station may confirm or reject the request. Thetemporary capability restriction may be transparent to 5GC (e.g., staticcapabilities may be stored in 5GC).

When CA is configured, a wireless device may have an RRC connection witha network. At RRC connection establishment/re-establishment/handoverprocedure, one serving cell may provide NAS mobility information, and atRRC connection re-establishment/handover, one serving cell may provide asecurity input. This cell may be referred to as the PCell. Depending onthe capabilities of the wireless device, SCells may be configured toform together with the PCell a set of serving cells. The configured setof serving cells for the wireless device may comprise one PCell and oneor more SCells.

The reconfiguration, addition and removal of SCells may be performed byRRC. At intra-NR handover, RRC may also add, remove, or reconfigureSCells for usage with the target PCell. When adding a new SCell,dedicated RRC signaling may be employed to send all required systeminformation of the SCell i.e. while in connected mode, wireless devicesmay not need to acquire broadcasted system information directly from theSCells.

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g. to establish, modify and/or release RBs,to perform handover, to setup, modify, and/or release measurements, toadd, modify, and/or release SCells and cell groups). As part of the RRCconnection reconfiguration procedure, NAS dedicated information may betransferred from the network to the wireless device. TheRRCConnectionReconfiguration message may be a command to modify an RRCconnection. It may convey information for measurement configuration,mobility control, radio resource configuration (e.g. RBs, MAC mainconfiguration and physical channel configuration) comprising anyassociated dedicated NAS information and security configuration. If thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList, the wireless device may perform an SCell release. Ifthe received RRC Connection Reconfiguration message includes thesCellToAddModList, the wireless device may perform SCell additions ormodification.

An RRC connection establishment (or reestablishment, resume) proceduremay be to establish (or reestablish, resume) an RRC connection. an RRCconnection establishment procedure may comprise SRB1 establishment. TheRRC connection establishment procedure may be used to transfer theinitial NAS dedicated information/message from a wireless device toE-UTRAN. The RRCConnectionReestablishment message may be used tore-establish SRB1.

A measurement report procedure may be to transfer measurement resultsfrom a wireless device to NG-RAN. The wireless device may initiate ameasurement report procedure after successful security activation. Ameasurement report message may be employed to transmit measurementresults.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g. a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 stored in non-transitory memory 315 and executable bythe at least one processor 314. The wireless device 110 may furthercomprise at least one of at least one speaker/microphone 311, at leastone keypad 312, at least one display/touchpad 313, at least one powersource 317, at least one global positioning system (GPS) chipset 318,and other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding/processing, data processing, powercontrol, input/output processing, and/or any other functionality thatmay enable the wireless device 110, the base station 1 120A and/or thebase station 2 120B to operate in a wireless environment.

The processor 314 of the wireless device 110 may be connected to thespeaker/microphone 311, the keypad 312, and/or the display/touchpad 313.The processor 314 may receive user input data from and/or provide useroutput data to the speaker/microphone 311, the keypad 312, and/or thedisplay/touchpad 313. The processor 314 in the wireless device 110 mayreceive power from the power source 317 and/or may be configured todistribute the power to the other components in the wireless device 110.The power source 317 may comprise at least one of one or more dry cellbatteries, solar cells, fuel cells, and the like. The processor 314 maybe connected to the GPS chipset 318. The GPS chipset 318 may beconfigured to provide geographic location information of the wirelessdevice 110.

The processor 314 of the wireless device 110 may further be connected toother peripherals 319, which may comprise one or more software and/orhardware modules that provide additional features and/orfunctionalities. For example, the peripherals 319 may comprise at leastone of an accelerometer, a satellite transceiver, a digital camera, auniversal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, and thelike.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110 via a wireless link 330A and/or a wireless link 330Brespectively. In an example, the communication interface 320A of thebase station 1, 120A, may communicate with the communication interface320B of the base station 2 and other RAN and core network nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110 and/or thebase station 2 120B and the wireless device 110 may be configured tosend and receive transport blocks via the wireless link 330A and/or viathe wireless link 330B, respectively. The wireless link 330A and/or thewireless link 330B may employ at least one frequency carrier. Accordingto some of various aspects of embodiments, transceiver(s) may beemployed. A transceiver may be a device that comprises both atransmitter and a receiver. Transceivers may be employed in devices suchas wireless devices, base stations, relay nodes, and/or the like.Example embodiments for radio technology implemented in thecommunication interface 310, 320A, 320B and the wireless link 330A, 330Bare illustrated in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6, FIG. 7A,FIG. 7B, FIG. 8, and associated text.

In an example, other nodes in a wireless network (e.g. AMF, UPF, SMF,etc.) may comprise one or more communication interfaces, one or moreprocessors, and memory storing instructions.

A node (e.g. wireless device, base station, AMF, SMF, UPF, servers,switches, antennas, and/or the like) may comprise one or moreprocessors, and memory storing instructions that when executed by theone or more processors causes the node to perform certain processesand/or functions. Example embodiments may enable operation ofsingle-carrier and/or multi-carrier communications. Other exampleembodiments may comprise a non-transitory tangible computer readablemedia comprising instructions executable by one or more processors tocause operation of single-carrier and/or multi-carrier communications.Yet other example embodiments may comprise an article of manufacturethat comprises a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a node to enable operation ofsingle-carrier and/or multi-carrier communications. The node may includeprocessors, memory, interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and code stored in and/or incommunication with a memory device to implement connections, electronicdevice operations, protocol(s), protocol layers, communication drivers,device drivers, hardware operations, combinations thereof, and/or thelike.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D are example diagrams for uplinkand downlink signal transmission as per an aspect of an embodiment ofthe present disclosure. FIG. 4A shows an example uplink transmitter forat least one physical channel. A baseband signal representing a physicaluplink shared channel may perform one or more functions. The one or morefunctions may comprise at least one of: scrambling; modulation ofscrambled bits to generate complex-valued symbols; mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers; transform precoding to generate complex-valued symbols;precoding of the complex-valued symbols; mapping of precodedcomplex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 4A. These functions are illustrated as examples andit is anticipated that other mechanisms may be implemented in variousembodiments.

An example structure for modulation and up-conversion to the carrierfrequency of the complex-valued SC-FDMA or CP-OFDM baseband signal foran antenna port and/or the complex-valued Physical Random Access CHannel(PRACH) baseband signal is shown in FIG. 4B. Filtering may be employedprior to transmission.

An example structure for downlink transmissions is shown in FIG. 4C. Thebaseband signal representing a downlink physical channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

In an example, a gNB may transmit a first symbol and a second symbol onan antenna port, to a wireless device. The wireless device may infer thechannel (e.g., fading gain, multipath delay, etc.) for conveying thesecond symbol on the antenna port, from the channel for conveying thefirst symbol on the antenna port. In an example, a first antenna portand a second antenna port may be quasi co-located if one or morelarge-scale properties of the channel over which a first symbol on thefirst antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;doppler spread; doppler shift; average gain; average delay; and/orspatial Receiving (Rx) parameters.

An example modulation and up-conversion to the carrier frequency of thecomplex-valued OFDM baseband signal for an antenna port is shown in FIG.4D. Filtering may be employed prior to transmission.

FIG. 5A is a diagram of an example uplink channel mapping and exampleuplink physical signals. FIG. 5B is a diagram of an example downlinkchannel mapping and a downlink physical signals. In an example, aphysical layer may provide one or more information transfer services toa MAC and/or one or more higher layers. For example, the physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and with what characteristics data are transferred over theradio interface.

In an example embodiment, a radio network may comprise one or moredownlink and/or uplink transport channels. For example, a diagram inFIG. 5A shows example uplink transport channels comprising Uplink-SharedCHannel (UL-SCH) 501 and Random Access CHannel (RACH) 502. A diagram inFIG. 5B shows example downlink transport channels comprisingDownlink-Shared CHannel (DL-SCH) 511, Paging CHannel (PCH) 512, andBroadcast CHannel (BCH) 513. A transport channel may be mapped to one ormore corresponding physical channels. For example, UL-SCH 501 may bemapped to Physical Uplink Shared CHannel (PUSCH) 503. RACH 502 may bemapped to PRACH 505. DL-SCH 511 and PCH 512 may be mapped to PhysicalDownlink Shared CHannel (PDSCH) 514. BCH 513 may be mapped to PhysicalBroadcast CHannel (PBCH) 516.

There may be one or more physical channels without a correspondingtransport channel. The one or more physical channels may be employed forUplink Control Information (UCI) 509 and/or Downlink Control Information(DCI) 517. For example, Physical Uplink Control CHannel (PUCCH) 504 maycarry UCI 509 from a UE to a base station. For example, PhysicalDownlink Control CHannel (PDCCH) 515 may carry DCI 517 from a basestation to a UE. NR may support UCI 509 multiplexing in PUSCH 503 whenUCI 509 and PUSCH 503 transmissions may coincide in a slot at least inpart. The UCI 509 may comprise at least one of CSI, Acknowledgement(ACK)/Negative Acknowledgement (NACK), and/or scheduling request. TheDCI 517 on PDCCH 515 may indicate at least one of following: one or moredownlink assignments and/or one or more uplink scheduling grants

In uplink, a UE may transmit one or more Reference Signals (RSs) to abase station. For example, the one or more RSs may be at least one ofDemodulation-RS (DM-RS) 506, Phase Tracking-RS (PT-RS) 507, and/orSounding RS (SRS) 508. In downlink, a base station may transmit (e.g.,unicast, multicast, and/or broadcast) one or more RSs to a UE. Forexample, the one or more RSs may be at least one of PrimarySynchronization Signal (PSS)/Secondary Synchronization Signal (SSS) 521,CSI-RS 522, DM-RS 523, and/or PT-RS 524.

In an example, a UE may transmit one or more uplink DM-RSs 506 to a basestation for channel estimation, for example, for coherent demodulationof one or more uplink physical channels (e.g., PUSCH 503 and/or PUCCH504). For example, a UE may transmit a base station at least one uplinkDM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at least oneuplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. In an example, a base station mayconfigure a UE with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to transmit at one or more symbols of a PUSCH and/or PUCCH. Abase station may semi-statistically configure a UE with a maximum numberof front-loaded DM-RS symbols for PUSCH and/or PUCCH. For example, a UEmay schedule a single-symbol DM-RS and/or double symbol DM-RS based on amaximum number of front-loaded DM-RS symbols, wherein a base station mayconfigure the UE with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, e.g., at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

In an example, whether uplink PT-RS 507 is present or not may depend ona RRC configuration. For example, a presence of uplink PT-RS may beUE-specifically configured. For example, a presence and/or a pattern ofuplink PT-RS 507 in a scheduled resource may be UE-specificallyconfigured by a combination of RRC signaling and/or association with oneor more parameters employed for other purposes (e.g., Modulation andCoding Scheme (MCS)) which may be indicated by DCI. When configured, adynamic presence of uplink PT-RS 507 may be associated with one or moreDCI parameters comprising at least MCS. A radio network may supportplurality of uplink PT-RS densities defined in time/frequency domain.When present, a frequency domain density may be associated with at leastone configuration of a scheduled bandwidth. A UE may assume a sameprecoding for a DMRS port and a PT-RS port. A number of PT-RS ports maybe fewer than a number of DM-RS ports in a scheduled resource. Forexample, uplink PT-RS 507 may be confined in the scheduledtime/frequency duration for a UE.

In an example, a UE may transmit SRS 508 to a base station for channelstate estimation to support uplink channel dependent scheduling and/orlink adaptation. For example, SRS 508 transmitted by a UE may allow fora base station to estimate an uplink channel state at one or moredifferent frequencies. A base station scheduler may employ an uplinkchannel state to assign one or more resource blocks of good quality foran uplink PUSCH transmission from a UE. A base station maysemi-statistically configure a UE with one or more SRS resource sets.For an SRS resource set, a base station may configure a UE with one ormore SRS resources. An SRS resource set applicability may be configuredby a higher layer (e.g., RRC) parameter. For example, when a higherlayer parameter indicates beam management, a SRS resource in each of oneor more SRS resource sets may be transmitted at a time instant. A UE maytransmit one or more SRS resources in different SRS resource setssimultaneously. A new radio network may support aperiodic, periodicand/or semi-persistent SRS transmissions. A UE may transmit SRSresources based on one or more trigger types, wherein the one or moretrigger types may comprise higher layer signaling (e.g., RRC) and/or oneor more DCI formats (e.g., at least one DCI format may be employed for aUE to select at least one of one or more configured SRS resource sets.An SRS trigger type 0 may refer to an SRS triggered based on a higherlayer signaling. An SRS trigger type 1 may refer to an SRS triggeredbased on one or more DCI formats. In an example, when PUSCH 503 and SRS508 are transmitted in a same slot, a UE may be configured to transmitSRS 508 after a transmission of PUSCH 503 and corresponding uplink DM-RS506.

In an example, a base station may semi-statistically configure a UE withone or more SRS configuration parameters indicating at least one offollowing: a SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, a SRS bandwidth, afrequency hopping bandwidth, a cyclic shift, and/or a SRS sequence ID.

In an example, in a time domain, an SS/PBCH block may comprise one ormore OFDM symbols (e.g., 4 OFDM symbols numbered in increasing orderfrom 0 to 3) within the SS/PBCH block. An SS/PBCH block may comprisePSS/SSS 521 and PBCH 516. In an example, in the frequency domain, anSS/PBCH block may comprise one or more contiguous subcarriers (e.g., 240contiguous subcarriers with the subcarriers numbered in increasing orderfrom 0 to 239) within the SS/PBCH block. For example, a PSS/SSS 521 mayoccupy 1 OFDM symbol and 127 subcarriers. For example, PBCH 516 may spanacross 3 OFDM symbols and 240 subcarriers. A UE may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, e.g., with respect to Doppler spread, Doppler shift, averagegain, average delay, and spatial Rx parameters. A UE may not assumequasi co-location for other SS/PBCH block transmissions. A periodicityof an SS/PBCH block may be configured by a radio network (e.g., by anRRC signaling) and one or more time locations where the SS/PBCH blockmay be sent may be determined by sub-carrier spacing. In an example, aUE may assume a band-specific sub-carrier spacing for an SS/PBCH blockunless a radio network has configured a UE to assume a differentsub-carrier spacing.

In an example, downlink CSI-RS 522 may be employed for a UE to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of downlink CSI-RS 522.For example, a base station may semi-statistically configure and/orreconfigure a UE with periodic transmission of downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated ad/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation ofCSI-RS resource may be triggered dynamically. In an example, CSI-RSconfiguration may comprise one or more parameters indicating at least anumber of antenna ports. For example, a base station may configure a UEwith 32 ports. A base station may semi-statistically configure a UE withone or more CSI-RS resource sets. One or more CSI-RS resources may beallocated from one or more CSI-RS resource sets to one or more UEs. Forexample, a base station may semi-statistically configure one or moreparameters indicating CSI RS resource mapping, for example, time-domainlocation of one or more CSI-RS resources, a bandwidth of a CSI-RSresource, and/or a periodicity. In an example, a UE may be configured toemploy a same OFDM symbols for downlink CSI-RS 522 and control resourceset (coreset) when the downlink CSI-RS 522 and coreset are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are the outside of PRBs configured for coreset. In anexample, a UE may be configured to employ a same OFDM symbols fordownlink CSI-RS 522 and SS/PBCH blocks when the downlink CSI-RS 522 andSS/PBCH blocks are spatially quasi co-located and resource elementsassociated with the downlink CSI-RS 522 are the outside of PRBsconfigured for SS/PBCH blocks.

In an example, a UE may transmit one or more downlink DM-RSs 523 to abase station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). For example, a radio network may support one or more variableand/or configurable DM-RS patterns for data demodulation. At least onedownlink DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-statisticallyconfigure a UE with a maximum number of front-loaded DM-RS symbols forPDSCH 514. For example, a DM-RS configuration may support one or moreDM-RS ports. For example, for single user-MIMO, a DM-RS configurationmay support at least 8 orthogonal downlink DM-RS ports. For example, formultiuser-MIMO, a DM-RS configuration may support 12 orthogonal downlinkDM-RS ports. A radio network may support, e.g., at least for CP-OFDM, acommon DM-RS structure for DL and UL, wherein a DM-RS location, DM-RSpattern, and/or scrambling sequence may be same or different.

In an example, whether downlink PT-RS 524 is present or not may dependon a RRC configuration. For example, a presence of downlink PT-RS 524may be UE-specifically configured. For example, a presence and/or apattern of downlink PT-RS 524 in a scheduled resource may beUE-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters employed for other purposes(e.g., MCS) which may be indicated by DCI. When configured, a dynamicpresence of downlink PT-RS 524 may be associated with one or more DCIparameters comprising at least MCS. A radio network may supportplurality of PT-RS densities defined in time/frequency domain. Whenpresent, a frequency domain density may be associated with at least oneconfiguration of a scheduled bandwidth. A UE may assume a same precodingfor a DMRS port and a PT-RS port. A number of PT-RS ports may be fewerthan a number of DM-RS ports in a scheduled resource. For example,downlink PT-RS 524 may be confined in the scheduled time/frequencyduration for a UE.

FIG. 6 is a diagram depicting an example transmission time and receptiontime for a carrier as per an aspect of an embodiment of the presentdisclosure. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers, in case ofcarrier aggregation, or ranging from 1 to 64 carriers, in case of dualconnectivity. Different radio frame structures may be supported (e.g.,for FDD and for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. In this example, radio frame duration is 10 ms. In thisexample, a 10 ms radio frame 601 may be divided into ten equally sizedsubframes 602 with 1 ms duration. Subframe(s) may comprise one or moreslots (e.g. slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6, a subframemay be divided into two equally sized slots 603 with 0.5 ms duration.For example, 10 subframes may be available for downlink transmission and10 subframes may be available for uplink transmissions in a 10 msinterval. Uplink and downlink transmissions may be separated in thefrequency domain. Slot(s) may include a plurality of OFDM symbols 604.The number of OFDM symbols 604 in a slot 605 may depend on the cyclicprefix length. For example, a slot may be 14 OFDM symbols for the samesubcarrier spacing of up to 480 kHz with normal CP. A slot may be 12OFDM symbols for the same subcarrier spacing of 60 kHz with extended CP.A slot may contain downlink, uplink, or a downlink part and an uplinkpart and/or alike.

FIG. 7A is a diagram depicting example sets of OFDM subcarriers as peran aspect of an embodiment of the present disclosure. In the example, agNB may communicate with a wireless device with a carrier with anexample channel bandwidth 700. Arrow(s) in the diagram may depict asubcarrier in a multicarrier OFDM system. The OFDM system may usetechnology such as OFDM technology, SC-FDMA technology, and/or the like.In an example, an arrow 701 shows a subcarrier transmitting informationsymbols. In an example, a subcarrier spacing 702, between two contiguoussubcarriers in a carrier, may be any one of 15 KHz, 30 KHz, 60 KHz, 120KHz, 240 KHz etc. In an example, different subcarrier spacing maycorrespond to different transmission numerologies. In an example, atransmission numerology may comprise at least: a numerology index; avalue of subcarrier spacing; a type of cyclic prefix (CP). In anexample, a gNB may transmit to/receive from a UE on a number ofsubcarriers 703 in a carrier. In an example, a bandwidth occupied by anumber of subcarriers 703 (transmission bandwidth) may be smaller thanthe channel bandwidth 700 of a carrier, due to guard band 704 and 705.In an example, a guard band 704 and 705 may be used to reduceinterference to and from one or more neighbor carriers. A number ofsubcarriers (transmission bandwidth) in a carrier may depend on thechannel bandwidth of the carrier and the subcarrier spacing. Forexample, a transmission bandwidth, for a carrier with 20 MHz channelbandwidth and 15 KHz subcarrier spacing, may be in number of 1024subcarriers.

In an example, a gNB and a wireless device may communicate with multipleCCs when configured with CA. In an example, different component carriersmay have different bandwidth and/or subcarrier spacing, if CA issupported. In an example, a gNB may transmit a first type of service toa UE on a first component carrier. The gNB may transmit a second type ofservice to the UE on a second component carrier. Different type ofservices may have different service requirement (e.g., data rate,latency, reliability), which may be suitable for transmission viadifferent component carrier having different subcarrier spacing and/orbandwidth. FIG. 7B shows an example embodiment. A first componentcarrier may comprise a first number of subcarriers 706 with a firstsubcarrier spacing 709. A second component carrier may comprise a secondnumber of subcarriers 707 with a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 with athird subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 is a diagram depicting OFDM radio resources as per an aspect ofan embodiment of the present disclosure. In an example, a carrier mayhave a transmission bandwidth 801. In an example, a resource grid may bein a structure of frequency domain 802 and time domain 803. In anexample, a resource grid may comprise a first number of OFDM symbols ina subframe and a second number of resource blocks, starting from acommon resource block indicated by higher-layer signaling (e.g. RRCsignaling), for a transmission numerology and a carrier. In an example,in a resource grid, a resource unit identified by a subcarrier index anda symbol index may be a resource element 805. In an example, a subframemay comprise a first number of OFDM symbols 807 depending on anumerology associated with a carrier. For example, when a subcarrierspacing of a numerology of a carrier is 15 KHz, a subframe may have 14OFDM symbols for a carrier. When a subcarrier spacing of a numerology is30 KHz, a subframe may have 28 OFDM symbols. When a subcarrier spacingof a numerology is 60 Khz, a subframe may have 56 OFDM symbols, etc. Inan example, a second number of resource blocks comprised in a resourcegrid of a carrier may depend on a bandwidth and a numerology of thecarrier.

As shown in FIG. 8, a resource block 806 may comprise 12 subcarriers. Inan example, multiple resource blocks may be grouped into a ResourceBlock Group (RBG) 804. In an example, a size of a RBG may depend on atleast one of: a RRC message indicating a RBG size configuration; a sizeof a carrier bandwidth; or a size of a bandwidth part of a carrier. Inan example, a carrier may comprise multiple bandwidth parts. A firstbandwidth part of a carrier may have different frequency location and/orbandwidth from a second bandwidth part of the carrier.

In an example, a gNB may transmit a downlink control informationcomprising a downlink or uplink resource block assignment to a wirelessdevice. A base station may transmit to or receive from, a wirelessdevice, data packets (e.g. transport blocks) scheduled and transmittedvia one or more resource blocks and one or more slots according toparameters in a downlink control information and/or RRC message(s). Inan example, a starting symbol relative to a first slot of the one ormore slots may be indicated to the wireless device. In an example, a gNBmay transmit to or receive from, a wireless device, data packetsscheduled on one or more RBGs and one or more slots.

In an example, a gNB may transmit a downlink control informationcomprising a downlink assignment to a wireless device via one or morePDCCHs. The downlink assignment may comprise parameters indicating atleast modulation and coding format; resource allocation; and/or HARQinformation related to DL-SCH. In an example, a resource allocation maycomprise parameters of resource block allocation; and/or slotallocation. In an example, a gNB may dynamically allocate resources to awireless device via a Cell-Radio Network Temporary Identifier (C-RNTI)on one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible allocation when its downlink receptionis enabled. The wireless device may receive one or more downlink datapackage on one or more PDSCH scheduled by the one or more PDCCHs, whensuccessfully detecting the one or more PDCCHs.

In an example, a gNB may allocate Configured Scheduling (CS) resourcesfor down link transmission to a wireless device. The gNB may transmitone or more RRC messages indicating a periodicity of the CS grant. ThegNB may transmit a DCI via a PDCCH addressed to a ConfiguredScheduling-RNTI (CS-RNTI) activating the CS resources. The DCI maycomprise parameters indicating that the downlink grant is a CS grant.The CS grant may be implicitly reused according to the periodicitydefined by the one or more RRC messages, until deactivated.

In an example, a gNB may transmit a downlink control informationcomprising an uplink grant to a wireless device via one or more PDCCHs.The uplink grant may comprise parameters indicating at least modulationand coding format; resource allocation; and/or HARQ information relatedto UL-SCH. In an example, a resource allocation may comprise parametersof resource block allocation; and/or slot allocation. In an example, agNB may dynamically allocate resources to a wireless device via a C-RNTIon one or more PDCCHs. The wireless device may monitor the one or morePDCCHs in order to find possible resource allocation. The wirelessdevice may transmit one or more uplink data package via one or morePUSCH scheduled by the one or more PDCCHs, when successfully detectingthe one or more PDCCHs.

In an example, a gNB may allocate CS resources for uplink datatransmission to a wireless device. The gNB may transmit one or more RRCmessages indicating a periodicity of the CS grant. The gNB may transmita DCI via a PDCCH addressed to a CS-RNTI activating the CS resources.The DCI may comprise parameters indicating that the uplink grant is a CSgrant. The CS grant may be implicitly reused according to theperiodicity defined by the one or more RRC message, until deactivated.

In an example, a base station may transmit DCI/control signaling viaPDCCH. The DCI may take a format in a plurality of formats. A DCI maycomprise downlink and/or uplink scheduling information (e.g., resourceallocation information, HARQ related parameters, MCS), request for CSI(e.g., aperiodic CQI reports), request for SRS, uplink power controlcommands for one or more cells, one or more timing information (e.g., TBtransmission/reception timing, HARQ feedback timing, etc.), etc. In anexample, a DCI may indicate an uplink grant comprising transmissionparameters for one or more transport blocks. In an example, a DCI mayindicate downlink assignment indicating parameters for receiving one ormore transport blocks. In an example, a DCI may be used by base stationto initiate a contention-free random access at the wireless device. Inan example, the base station may transmit a DCI comprising slot formatindicator (SFI) notifying a slot format. In an example, the base stationmay transmit a DCI comprising pre-emption indication notifying thePRB(s) and/or OFDM symbol(s) where a UE may assume no transmission isintended for the UE. In an example, the base station may transmit a DCIfor group power control of PUCCH or PUSCH or SRS. In an example, a DCImay correspond to an RNTI. In an example, the wireless device may obtainan RNTI in response to completing the initial access (e.g., C-RNTI). Inan example, the base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI). In an example, the wireless device may compute an RNTI(e.g., the wireless device may compute RA-RNTI based on resources usedfor transmission of a preamble). In an example, an RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). In an example, awireless device may monitor a group common search space which may beused by base station for transmitting DCIs that are intended for a groupof UEs. In an example, a group common DCI may correspond to an RNTIwhich is commonly configured for a group of UEs. In an example, awireless device may monitor a UE-specific search space. In an example, aUE specific DCI may correspond to an RNTI configured for the wirelessdevice.

A NR system may support a single beam operation and/or a multi-beamoperation. In a multi-beam operation, a base station may perform adownlink beam sweeping to provide coverage for common control channelsand/or downlink SS blocks, which may comprise at least a PSS, a SSS,and/or PBCH. A wireless device may measure quality of a beam pair linkusing one or more RSs. One or more SS blocks, or one or more CSI-RSresources, associated with a CSI-RS resource index (CRI), or one or moreDM-RSs of PBCH, may be used as RS for measuring quality of a beam pairlink. Quality of a beam pair link may be defined as a reference signalreceived power (RSRP) value, or a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. A RS resource and DM-RSs of a control channel may be calledQCLed when a channel characteristics from a transmission on an RS to awireless device, and that from a transmission on a control channel to awireless device, are similar or same under a configured criterion. In amulti-beam operation, a wireless device may perform an uplink beamsweeping to access a cell.

In an example, a wireless device may be configured to monitor PDCCH onone or more beam pair links simultaneously depending on a capability ofa wireless device. This may increase robustness against beam pair linkblocking. A base station may transmit one or more messages to configurea wireless device to monitor PDCCH on one or more beam pair links indifferent PDCCH OFDM symbols. For example, a base station may transmithigher layer signaling (e.g. RRC signaling) or MAC CE comprisingparameters related to the Rx beam setting of a wireless device formonitoring PDCCH on one or more beam pair links. A base station maytransmit indication of spatial QCL assumption between an DL RS antennaport(s) (for example, cell-specific CSI-RS, or wireless device-specificCSI-RS, or SS block, or PBCH with or without DM-RSs of PBCH), and DL RSantenna port(s) for demodulation of DL control channel. Signaling forbeam indication for a PDCCH may be MAC CE signaling, or RRC signaling,or DCI signaling, or specification-transparent and/or implicit method,and combination of these signaling methods.

For reception of unicast DL data channel, a base station may indicatespatial QCL parameters between DL RS antenna port(s) and DM-RS antennaport(s) of DL data channel. The base station may transmit DCI (e.g.downlink grants) comprising information indicating the RS antennaport(s). The information may indicate RS antenna port(s) which may beQCLed with the DM-RS antenna port(s). Different set of DM-RS antennaport(s) for a DL data channel may be indicated as QCL with different setof the RS antenna port(s).

FIG. 9A is an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. For example, in a multi-beamoperation, a base station 120 may transmit SS blocks in multiple beams,together forming a SS burst 940. One or more SS blocks may betransmitted on one beam. If multiple SS bursts 940 are transmitted withmultiple beams, SS bursts together may form SS burst set 950.

A wireless device may further use CSI-RS in the multi-beam operation forestimating a beam quality of a links between a wireless device and abase station. A beam may be associated with a CSI-RS. For example, awireless device may, based on a RSRP measurement on CSI-RS, report abeam index, as indicated in a CRI for downlink beam selection, andassociated with a RSRP value of a beam. A CSI-RS may be transmitted on aCSI-RS resource including at least one of one or more antenna ports, oneor more time or frequency radio resources. A CSI-RS resource may beconfigured in a cell-specific way by common RRC signaling, or in awireless device-specific way by dedicated RRC signaling, and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be transmitted periodically, or using aperiodictransmission, or using a multi-shot or semi-persistent transmission. Forexample, in a periodic transmission in FIG. 9A, a base station 120 maytransmit configured CSI-RS resources 940 periodically using a configuredperiodicity in a time domain. In an aperiodic transmission, a configuredCSI-RS resource may be transmitted in a dedicated time slot. In amulti-shot or semi-persistent transmission, a configured CSI-RS resourcemay be transmitted within a configured period. Beams used for CSI-RStransmission may have different beam width than beams used for SS-blockstransmission.

FIG. 9B is an example of a beam management procedure in an example newradio network. A base station 120 and/or a wireless device 110 mayperform a downlink L1/L2 beam management procedure. One or more of thefollowing downlink L1/L2 beam management procedures may be performedwithin one or more wireless devices 110 and one or more base stations120. In an example, a P-1 procedure 910 may be used to enable thewireless device 110 to measure one or more Transmission (Tx) beamsassociated with the base station 120 to support a selection of a firstset of Tx beams associated with the base station 120 and a first set ofRx beam(s) associated with a wireless device 110. For beamforming at abase station 120, a base station 120 may sweep a set of different TXbeams. For beamforming at a wireless device 110, a wireless device 110may sweep a set of different Rx beams. In an example, a P-2 procedure920 may be used to enable a wireless device 110 to measure one or moreTx beams associated with a base station 120 to possibly change a firstset of Tx beams associated with a base station 120. A P-2 procedure 920may be performed on a possibly smaller set of beams for beam refinementthan in the P-1 procedure 910. A P-2 procedure 920 may be a special caseof a P-1 procedure 910. In an example, a P-3 procedure 930 may be usedto enable a wireless device 110 to measure at least one Tx beamassociated with a base station 120 to change a first set of Rx beamsassociated with a wireless device 110.

A wireless device 110 may transmit one or more beam management reportsto a base station 120. In one or more beam management reports, awireless device 110 may indicate some beam pair quality parameters,comprising at least, one or more beam identifications; RSRP; PrecodingMatrix Indicator (PMI)/Channel Quality Indicator (CQI)/Rank Indicator(RI) of a subset of configured beams. Based on one or more beammanagement reports, a base station 120 may transmit to a wireless device110 a signal indicating that one or more beam pair links are one or moreserving beams. A base station 120 may transmit PDCCH and PDSCH for awireless device 110 using one or more serving beams.

In an example embodiment, new radio network may support a BandwidthAdaptation (BA). In an example, receive and/or transmit bandwidthsconfigured by an UE employing a BA may not be large. For example, areceive and/or transmit bandwidths may not be as large as a bandwidth ofa cell. Receive and/or transmit bandwidths may be adjustable. Forexample, a UE may change receive and/or transmit bandwidths, e.g., toshrink during period of low activity to save power. For example, a UEmay change a location of receive and/or transmit bandwidths in afrequency domain, e.g. to increase scheduling flexibility. For example,a UE may change a subcarrier spacing, e.g. to allow different services.

In an example embodiment, a subset of a total cell bandwidth of a cellmay be referred to as a Bandwidth Part (BWP). A base station mayconfigure a UE with one or more BWPs to achieve a BA. For example, abase station may indicate, to a UE, which of the one or more(configured) BWPs is an active BWP.

FIG. 10 is an example diagram of 3 BWPs configured: BWP1 (1010 and 1050)with a width of 40 MHz and subcarrier spacing of 15 kHz; BWP2 (1020 and1040) with a width of 10 MHz and subcarrier spacing of 15 kHz; BWP3 1030with a width of 20 MHz and subcarrier spacing of 60 kHz.

In an example, a UE, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g. RRC layer)for a cell a set of one or more BWPs (e.g., at most four BWPs) forreceptions by the UE (DL BWP set) in a DL bandwidth by at least oneparameter DL-BWP and a set of one or more BWPs (e.g., at most four BWPs)for transmissions by a UE (UL BWP set) in an UL bandwidth by at leastone parameter UL-BWP for a cell.

To enable BA on the PCell, a base station may configure a UE with one ormore UL and DL BWP pairs. To enable BA on SCells (e.g., in case of CA),a base station may configure a UE at least with one or more DL BWPs(e.g., there may be none in an UL).

In an example, an initial active DL BWP may be defined by at least oneof a location and number of contiguous PRBs, a subcarrier spacing, or acyclic prefix, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a UE is configured with a secondary carrier on a primary cell, the UEmay be configured with an initial BWP for random access procedure on asecondary carrier.

In an example, for unpaired spectrum operation, a UE may expect that acenter frequency for a DL BWP may be same as a center frequency for a ULBWP.

For example, for a DL BWP or an UL BWP in a set of one or more DL BWPsor one or more UL BWPs, respectively, a base station maysemi-statistically configure a UE for a cell with one or more parametersindicating at least one of following: a subcarrier spacing; a cyclicprefix; a number of contiguous PRBs; an index in the set of one or moreDL BWPs and/or one or more UL BWPs; a link between a DL BWP and an ULBWP from a set of configured DL BWPs and UL BWPs; a DCI detection to aPDSCH reception timing; a PDSCH reception to a HARQ-ACK transmissiontiming value; a DCI detection to a PUSCH transmission timing value; anoffset of a first PRB of a DL bandwidth or an UL bandwidth,respectively, relative to a first PRB of a bandwidth.

In an example, for a DL BWP in a set of one or more DL BWPs on a PCell,a base station may configure a UE with one or more control resource setsfor at least one type of common search space and/or one UE-specificsearch space. For example, a base station may not configure a UE withouta common search space on a PCell, or on a PSCell, in an active DL BWP.

For an UL BWP in a set of one or more UL BWPs, a base station mayconfigure a UE with one or more resource sets for one or more PUCCHtransmissions.

In an example, if a DCI comprises a BWP indicator field, a BWP indicatorfield value may indicate an active DL BWP, from a configured DL BWP set,for one or more DL receptions. If a DCI comprises a BWP indicator field,a BWP indicator field value may indicate an active UL BWP, from aconfigured UL BWP set, for one or more UL transmissions.

In an example, for a PCell, a base station may semi-statisticallyconfigure a UE with a default DL BWP among configured DL BWPs. If a UEis not provided a default DL BWP, a default BWP may be an initial activeDL BWP.

In an example, a base station may configure a UE with a timer value fora PCell. For example, a UE may start a timer, referred to as BWPinactivity timer, when a UE detects a DCI indicating an active DL BWP,other than a default DL BWP, for a paired spectrum operation or when aUE detects a DCI indicating an active DL BWP or UL BWP, other than adefault DL BWP or UL BWP, for an unpaired spectrum operation. The UE mayincrement the timer by an interval of a first value (e.g., the firstvalue may be 1 millisecond or 0.5 milliseconds) if the UE does notdetect a DCI during the interval for a paired spectrum operation or foran unpaired spectrum operation. In an example, the timer may expire whenthe timer is equal to the timer value. A UE may switch to the default DLBWP from an active DL BWP when the timer expires.

In an example, a base station may semi-statistically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of BWP inactivity timer(for example, the second BWP may be a default BWP). For example, FIG. 10is an example diagram of 3 BWPs configured, BWP1 (1010 and 1050), BWP2(1020 and 1040), and BWP3 (1030). BWP2 (1020 and 1040) may be a defaultBWP. BWP1 (1010) may be an initial active BWP. In an example, a UE mayswitch an active BWP from BWP1 1010 to BWP2 1020 in response to anexpiry of BWP inactivity timer. For example, a UE may switch an activeBWP from BWP2 1020 to BWP3 1030 in response to receiving a DCIindicating BWP3 1030 as an active BWP. Switching an active BWP from BWP31030 to BWP2 1040 and/or from BWP2 1040 to BWP1 1050 may be in responseto receiving a DCI indicating an active BWP and/or in response to anexpiry of BWP inactivity timer.

In an example, if a UE is configured for a secondary cell with a defaultDL BWP among configured DL BWPs and a timer value, UE procedures on asecondary cell may be same as on a primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a base station configures a UE with a first active DLBWP and a first active UL BWP on a secondary cell or carrier, a UE mayemploy an indicated DL BWP and an indicated UL BWP on a secondary cellas a respective first active DL BWP and first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows employing a multi connectivity(e.g. dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A is an example diagram of a protocol structure of awireless device 110 (e.g. UE) with CA and/or multi connectivity as peran aspect of an embodiment. FIG. 11B is an example diagram of a protocolstructure of multiple base stations with CA and/or multi connectivity asper an aspect of an embodiment. The multiple base stations may comprisea master node, MN 1130 (e.g. a master node, a master base station, amaster gNB, a master eNB, and/or the like) and a secondary node, SN 1150(e.g. a secondary node, a secondary base station, a secondary gNB, asecondary eNB, and/or the like). A master node 1130 and a secondary node1150 may co-work to communicate with a wireless device 110.

When multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception/transmissionfunctions in an RRC connected state, may be configured to utilize radioresources provided by multiple schedulers of a multiple base stations.Multiple base stations may be inter-connected via a non-ideal or idealbackhaul (e.g. Xn interface, X2 interface, and/or the like). A basestation involved in multi connectivity for a certain wireless device mayperform at least one of two different roles: a base station may eitheract as a master base station or as a secondary base station. In multiconnectivity, a wireless device may be connected to one master basestation and one or more secondary base stations. In an example, a masterbase station (e.g. the MN 1130) may provide a master cell group (MCG)comprising a primary cell and/or one or more secondary cells for awireless device (e.g. the wireless device 110). A secondary base station(e.g. the SN 1150) may provide a secondary cell group (SCG) comprising aprimary secondary cell (PSCell) and/or one or more secondary cells for awireless device (e.g. the wireless device 110).

In multi connectivity, a radio protocol architecture that a beareremploys may depend on how a bearer is setup. In an example, threedifferent type of bearer setup options may be supported: an MCG bearer,an SCG bearer, and/or a split bearer. A wireless device mayreceive/transmit packets of an MCG bearer via one or more cells of theMCG, and/or may receive/transmits packets of an SCG bearer via one ormore cells of an SCG. Multi-connectivity may also be described as havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not beconfigured/implemented in some of the example embodiments.

In an example, a wireless device (e.g. Wireless Device 110) may transmitand/or receive: packets of an MCG bearer via an SDAP layer (e.g. SDAP1110), a PDCP layer (e.g. NR PDCP 1111), an RLC layer (e.g. MN RLC1114), and a MAC layer (e.g. MN MAC 1118); packets of a split bearer viaan SDAP layer (e.g. SDAP 1110), a PDCP layer (e.g. NR PDCP 1112), one ofa master or secondary RLC layer (e.g. MN RLC 1115, SN RLC 1116), and oneof a master or secondary MAC layer (e.g. MN MAC 1118, SN MAC 1119);and/or packets of an SCG bearer via an SDAP layer (e.g. SDAP 1110), aPDCP layer (e.g. NR PDCP 1113), an RLC layer (e.g. SN RLC 1117), and aMAC layer (e.g. MN MAC 1119).

In an example, a master base station (e.g. MN 1130) and/or a secondarybase station (e.g. SN 1150) may transmit/receive: packets of an MCGbearer via a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g. NR PDCP 1121, NR PDCP1142), a master node RLC layer (e.g. MN RLC 1124, MN RLC 1125), and amaster node MAC layer (e.g. MN MAC 1128); packets of an SCG bearer via amaster or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1122, NR PDCP 1143), asecondary node RLC layer (e.g. SN RLC 1146, SN RLC 1147), and asecondary node MAC layer (e.g. SN MAC 1148); packets of a split bearervia a master or secondary node SDAP layer (e.g. SDAP 1120, SDAP 1140), amaster or secondary node PDCP layer (e.g. NR PDCP 1123, NR PDCP 1141), amaster or secondary node RLC layer (e.g. MN RLC 1126, SN RLC 1144, SNRLC 1145, MN RLC 1127), and a master or secondary node MAC layer (e.g.MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities: one MAC entity (e.g. MN MAC 1118) for a master base station,and other MAC entities (e.g. SN MAC 1119) for a secondary base station.In multi-connectivity, a configured set of serving cells for a wirelessdevice may comprise two subsets: an MCG comprising serving cells of amaster base station, and SCGs comprising serving cells of a secondarybase station. For an SCG, one or more of following configurations may beapplied: at least one cell of an SCG has a configured UL CC and at leastone cell of a SCG, named as primary secondary cell (PSCell, PCell ofSCG, or sometimes called PCell), is configured with PUCCH resources;when an SCG is configured, there may be at least one SCG bearer or oneSplit bearer; upon detection of a physical layer problem or a randomaccess problem on a PSCell, or a number of NR RLC retransmissions hasbeen reached associated with the SCG, or upon detection of an accessproblem on a PSCell during a SCG addition or a SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, forsplit bearer, a DL data transfer over a master base station may bemaintained; an NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer; PCell and/or PSCell may not be de-activated; PSCellmay be changed with a SCG change procedure (e.g. with security keychange and a RACH procedure); and/or a bearer type change between asplit bearer and a SCG bearer or simultaneous configuration of a SCG anda split bearer may or may not supported.

With respect to interaction between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be applied: a master base station and/or a secondary basestation may maintain Radio Resource Management (RRM) measurementconfigurations of a wireless device; a master base station may (e.g.based on received measurement reports, traffic conditions, and/or bearertypes) may decide to request a secondary base station to provideadditional resources (e.g. serving cells) for a wireless device; uponreceiving a request from a master base station, a secondary base stationmay create/modify a container that may result in configuration ofadditional serving cells for a wireless device (or decide that thesecondary base station has no resource available to do so); for a UEcapability coordination, a master base station may provide (a part of)an AS configuration and UE capabilities to a secondary base station; amaster base station and a secondary base station may exchangeinformation about a UE configuration by employing of RRC containers(inter-node messages) carried via Xn messages; a secondary base stationmay initiate a reconfiguration of the secondary base station existingserving cells (e.g. PUCCH towards the secondary base station); asecondary base station may decide which cell is a PSCell within a SCG; amaster base station may or may not change content of RRC configurationsprovided by a secondary base station; in case of a SCG addition and/or aSCG SCell addition, a master base station may provide recent (or thelatest) measurement results for SCG cell(s); a master base station andsecondary base stations may receive information of SFN and/or subframeoffset of each other from OAM and/or via an Xn interface, (e.g. for apurpose of DRX alignment and/or identification of a measurement gap). Inan example, when adding a new SCG SCell, dedicated RRC signaling may beused for sending required system information of a cell as for CA, exceptfor a SFN acquired from a MIB of a PSCell of a SCG.

FIG. 12 is an example diagram of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival during RRC_CONNECTED when UL synchronization status isnon-synchronized, transition from RRC_Inactive, and/or request for othersystem information. For example, a PDCCH order, a MAC entity, and/or abeam failure indication may initiate a random access procedure.

In an example embodiment, a random access procedure may be at least oneof a contention based random access procedure and a contention freerandom access procedure. For example, a contention based random accessprocedure may comprise, one or more Msg 1 1220 transmissions, one ormore Msg2 1230 transmissions, one or more Msg3 1240 transmissions, andcontention resolution 1250. For example, a contention free random accessprocedure may comprise one or more Msg 1 1220 transmissions and one ormore Msg2 1230 transmissions.

In an example, a base station may transmit (e.g., unicast, multicast, orbroadcast), to a UE, a RACH configuration 1210 via one or more beams.The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: available set of PRACH resourcesfor a transmission of a random access preamble, initial preamble power(e.g., random access preamble initial received target power), an RSRPthreshold for a selection of a SS block and corresponding PRACHresource, a power-ramping factor (e.g., random access preamble powerramping step), random access preamble index, a maximum number ofpreamble transmission, preamble group A and group B, a threshold (e.g.,message size) to determine the groups of random access preambles, a setof one or more random access preambles for system information requestand corresponding PRACH resource(s), if any, a set of one or more randomaccess preambles for beam failure recovery request and correspondingPRACH resource(s), if any, a time window to monitor RA response(s), atime window to monitor response(s) on beam failure recovery request,and/or a contention resolution timer.

In an example, the Msg1 1220 may be one or more transmissions of arandom access preamble. For a contention based random access procedure,a UE may select a SS block with a RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a UE may select one or morerandom access preambles from a group A or a group B depending on apotential Msg3 1240 size. If a random access preambles group B does notexist, a UE may select the one or more random access preambles from agroup A. A UE may select a random access preamble index randomly (e.g.with equal probability or a normal distribution) from one or more randomaccess preambles associated with a selected group. If a base stationsemi-statistically configures a UE with an association between randomaccess preambles and SS blocks, the UE may select a random accesspreamble index randomly with equal probability from one or more randomaccess preambles associated with a selected SS block and a selectedgroup.

For example, a UE may initiate a contention free random access procedurebased on a beam failure indication from a lower layer. For example, abase station may semi-statistically configure a UE with one or morecontention free PRACH resources for beam failure recovery requestassociated with at least one of SS blocks and/or CSI-RSs. If at leastone of SS blocks with a RSRP above a first RSRP threshold amongstassociated SS blocks or at least one of CSI-RSs with a RSRP above asecond RSRP threshold amongst associated CSI-RSs is available, a UE mayselect a random access preamble index corresponding to a selected SSblock or CSI-RS from a set of one or more random access preambles forbeam failure recovery request.

For example, a UE may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. If a base station does not configure a UE with at least onecontention free PRACH resource associated with SS blocks or CSI-RS, theUE may select a random access preamble index. If a base stationconfigures a UE with one or more contention free PRACH resourcesassociated with SS blocks and at least one SS block with a RSRP above afirst RSRP threshold amongst associated SS blocks is available, the UEmay select the at least one SS block and select a random access preamblecorresponding to the at least one SS block. If a base station configuresa UE with one or more contention free PRACH resources associated withCSI-RSs and at least one CSI-RS with a RSRP above a second RSPRthreshold amongst the associated CSI-RSs is available, the UE may selectthe at least one CSI-RS and select a random access preamblecorresponding to the at least one CSI-RS.

A UE may perform one or more Msg1 1220 transmissions by transmitting theselected random access preamble. For example, if a UE selects an SSblock and is configured with an association between one or more PRACHoccasions and one or more SS blocks, the UE may determine an PRACHoccasion from one or more PRACH occasions corresponding to a selected SSblock. For example, if a UE selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs,the UE may determine a PRACH occasion from one or more PRACH occasionscorresponding to a selected CSI-RS. A UE may transmit, to a basestation, a selected random access preamble via a selected PRACHoccasions. A UE may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. A UE may determine a RA-RNTIassociated with a selected PRACH occasions in which a selected randomaccess preamble is transmitted. For example, a UE may not determine aRA-RNTI for a beam failure recovery request. A UE may determine anRA-RNTI at least based on an index of a first OFDM symbol and an indexof a first slot of a selected PRACH occasions, and/or an uplink carrierindex for a transmission of Msg1 1220.

In an example, a UE may receive, from a base station, a random accessresponse, Msg 2 1230. A UE may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For beam failurerecovery request, a base station may configure a UE with a differenttime window (e.g., bfr-ResponseWindow) to monitor response on beamfailure recovery request. For example, a UE may start a time window(e.g., ra-ResponseWindow or bfr-ResponseWindow) at a start of a firstPDCCH occasion after a fixed duration of one or more symbols from an endof a preamble transmission. If a UE transmits multiple preambles, the UEmay start a time window at a start of a first PDCCH occasion after afixed duration of one or more symbols from an end of a first preambletransmission. A UE may monitor a PDCCH of a cell for at least one randomaccess response identified by a RA-RNTI or for at least one response tobeam failure recovery request identified by a C-RNTI while a timer for atime window is running.

In an example, a UE may consider a reception of random access responsesuccessful if at least one random access response comprises a randomaccess preamble identifier corresponding to a random access preambletransmitted by the UE. A UE may consider the contention free randomaccess procedure successfully completed if a reception of random accessresponse is successful. If a contention free random access procedure istriggered for a beam failure recovery request, a UE may consider acontention free random access procedure successfully complete if a PDCCHtransmission is addressed to a C-RNTI. In an example, if at least onerandom access response comprises a random access preamble identifier, aUE may consider the random access procedure successfully completed andmay indicate a reception of an acknowledgement for a system informationrequest to upper layers. If a UE has signaled multiple preambletransmissions, the UE may stop transmitting remaining preambles (if any)in response to a successful reception of a corresponding random accessresponse.

In an example, a UE may perform one or more Msg 3 1240 transmissions inresponse to a successful reception of random access response (e.g., fora contention based random access procedure). A UE may adjust an uplinktransmission timing based on a timing advanced command indicated by arandom access response and may transmit one or more transport blocksbased on an uplink grant indicated by a random access response.Subcarrier spacing for PUSCH transmission for Msg3 1240 may be providedby at least one higher layer (e.g. RRC) parameter. A UE may transmit arandom access preamble via PRACH and Msg3 1240 via PUSCH on a same cell.A base station may indicate an UL BWP for a PUSCH transmission of Msg31240 via system information block. A UE may employ HARQ for aretransmission of Msg 3 1240.

In an example, multiple UEs may perform Msg 1 1220 by transmitting asame preamble to a base station and receive, from the base station, asame random access response comprising an identity (e.g., TC-RNTI).Contention resolution 1250 may ensure that a UE does not incorrectly usean identity of another UE. For example, contention resolution 1250 maybe based on C-RNTI on PDCCH or a UE contention resolution identity onDL-SCH. For example, if a base station assigns a C-RNTI to a UE, the UEmay perform contention resolution 1250 based on a reception of a PDCCHtransmission that is addressed to the C-RNTI. In response to detectionof a C-RNTI on a PDCCH, a UE may consider contention resolution 1250successful and may consider a random access procedure successfullycompleted. If a UE has no valid C-RNTI, a contention resolution may beaddressed by employing a TC-RNTI. For example, if a MAC PDU issuccessfully decoded and a MAC PDU comprises a UE contention resolutionidentity MAC CE that matches the CCCH SDU transmitted in Msg3 1250, a UEmay consider the contention resolution 1250 successful and may considerthe random access procedure successfully completed.

FIG. 13 is an example structure for MAC entities as per an aspect of anembodiment. In an example, a wireless device may be configured tooperate in a multi-connectivity mode. A wireless device in RRC_CONNECTEDwith multiple RX/TX may be configured to utilize radio resourcesprovided by multiple schedulers located in a plurality of base stations.The plurality of base stations may be connected via a non-ideal or idealbackhaul over the Xn interface. In an example, a base station in aplurality of base stations may act as a master base station or as asecondary base station. A wireless device may be connected to one masterbase station and one or more secondary base stations. A wireless devicemay be configured with multiple MAC entities, e.g. one MAC entity formaster base station, and one or more other MAC entities for secondarybase station(s). In an example, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 illustrates an examplestructure for MAC entities when MCG and SCG are configured for awireless device.

In an example, at least one cell in a SCG may have a configured UL CC,wherein a cell of at least one cell may be called PSCell or PCell ofSCG, or sometimes may be simply called PCell. A PSCell may be configuredwith PUCCH resources. In an example, when a SCG is configured, there maybe at least one SCG bearer or one split bearer. In an example, upondetection of a physical layer problem or a random access problem on aPSCell, or upon reaching a number of RLC retransmissions associated withthe SCG, or upon detection of an access problem on a PSCell during a SCGaddition or a SCG change: an RRC connection re-establishment proceduremay not be triggered, UL transmissions towards cells of an SCG may bestopped, a master base station may be informed by a UE of a SCG failuretype and DL data transfer over a master base station may be maintained.

In an example, a MAC sublayer may provide services such as data transferand radio resource allocation to upper layers (e.g. 1310 or 1320). A MACsublayer may comprise a plurality of MAC entities (e.g. 1350 and 1360).A MAC sublayer may provide data transfer services on logical channels.To accommodate different kinds of data transfer services, multiple typesof logical channels may be defined. A logical channel may supporttransfer of a particular type of information. A logical channel type maybe defined by what type of information (e.g., control or data) istransferred. For example, BCCH, PCCH, CCCH and DCCH may be controlchannels and DTCH may be a traffic channel. In an example, a first MACentity (e.g. 1310) may provide services on PCCH, BCCH, CCCH, DCCH, DTCHand MAC control elements. In an example, a second MAC entity (e.g. 1320)may provide services on BCCH, DCCH, DTCH and MAC control elements.

A MAC sublayer may expect from a physical layer (e.g. 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,signaling of scheduling request or measurements (e.g. CQI). In anexample, in dual connectivity, two MAC entities may be configured for awireless device: one for MCG and one for SCG. A MAC entity of wirelessdevice may handle a plurality of transport channels. In an example, afirst MAC entity may handle first transport channels comprising a PCCHof MCG, a first BCH of MCG, one or more first DL-SCHs of MCG, one ormore first UL-SCHs of MCG and one or more first RACHs of MCG. In anexample, a second MAC entity may handle second transport channelscomprising a second BCH of SCG, one or more second DL-SCHs of SCG, oneor more second UL-SCHs of SCG and one or more second RACHs of SCG.

In an example, if a MAC entity is configured with one or more SCells,there may be multiple DL-SCHs and there may be multiple UL-SCHs as wellas multiple RACHs per MAC entity. In an example, there may be one DL-SCHand UL-SCH on a SpCell. In an example, there may be one DL-SCH, zero orone UL-SCH and zero or one RACH for an SCell. A DL-SCH may supportreceptions using different numerologies and/or TTI duration within a MACentity. A UL-SCH may also support transmissions using differentnumerologies and/or TTI duration within the MAC entity.

In an example, a MAC sublayer may support different functions and maycontrol these functions with a control (e.g. 1355 or 1365) element.Functions performed by a MAC entity may comprise mapping between logicalchannels and transport channels (e.g., in uplink or downlink),multiplexing (e.g. 1352 or 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TB) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g. 1352 or 1362) of MAC SDUs to one or different logical channelsfrom transport blocks (TB) delivered from the physical layer ontransport channels (e.g., in downlink), scheduling information reporting(e.g., in uplink), error correction through HARQ in uplink or downlink(e.g. 1363), and logical channel prioritization in uplink (e.g. 1351 or1361). A MAC entity may handle a random access process (e.g. 1354 or1364).

FIG. 14 is an example diagram of a RAN architecture comprising one ormore base stations. In an example, a protocol stack (e.g. RRC, SDAP,PDCP, RLC, MAC, and PHY) may be supported at a node. A base station(e.g. gNB 120A or 120B) may comprise a base station central unit (CU)(e.g. gNB-CU 1420A or 1420B) and at least one base station distributedunit (DU) (e.g. gNB-DU 1430A, 1430B, 1430C, or 1430D) if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g. CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. In an example, an Xn interface may be configuredbetween base station CUs.

In an example, a base station CU may comprise an RRC function, an SDAPlayer, and a PDCP layer, and base station DUs may comprise an RLC layer,a MAC layer, and a PHY layer. In an example, various functional splitoptions between a base station CU and base station DUs may be possibleby locating different combinations of upper protocol layers (RANfunctions) in a base station CU and different combinations of lowerprotocol layers (RAN functions) in base station DUs. A functional splitmay support flexibility to move protocol layers between a base stationCU and base station DUs depending on service requirements and/or networkenvironments.

In an example, functional split options may be configured per basestation, per base station CU, per base station DU, per UE, per bearer,per slice, or with other granularities. In per base station CU split, abase station CU may have a fixed split option, and base station DUs maybe configured to match a split option of a base station CU. In per basestation DU split, a base station DU may be configured with a differentsplit option, and a base station CU may provide different split optionsfor different base station DUs. In per UE split, a base station (basestation CU and at least one base station DUs) may provide differentsplit options for different wireless devices. In per bearer split,different split options may be utilized for different bearers. In perslice splice, different split options may be applied for differentslices.

FIG. 15 is an example diagram showing RRC state transitions of awireless device. In an example, a wireless device may be in at least oneRRC state among an RRC connected state (e.g. RRC Connected 1530,RRC_Connected), an RRC idle state (e.g. RRC Idle 1510, RRC_Idle), and/oran RRC inactive state (e.g. RRC_Inactive 1520, RRC_Inactive). In anexample, in an RRC connected state, a wireless device may have at leastone RRC connection with at least one base station (e.g. gNB and/or eNB),which may have a UE context of the wireless device. A UE context (e.g. awireless device context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an example, in an RRC idle state, a wireless device may nothave an RRC connection with a base station, and a UE context of awireless device may not be stored in a base station. In an example, inan RRC inactive state, a wireless device may not have an RRC connectionwith a base station. A UE context of a wireless device may be stored ina base station, which may be called as an anchor base station (e.g. lastserving base station).

In an example, a wireless device may transition a UE RRC state betweenan RRC idle state and an RRC connected state in both ways (e.g.connection release 1540 or connection establishment 1550; or connectionreestablishment) and/or between an RRC inactive state and an RRCconnected state in both ways (e.g. connection inactivation 1570 orconnection resume 1580). In an example, a wireless device may transitionits RRC state from an RRC inactive state to an RRC idle state (e.g.connection release 1560).

In an example, an anchor base station may be a base station that maykeep a UE context (a wireless device context) of a wireless device atleast during a time period that a wireless device stays in a RANnotification area (RNA) of an anchor base station, and/or that awireless device stays in an RRC inactive state. In an example, an anchorbase station may be a base station that a wireless device in an RRCinactive state was lastly connected to in a latest RRC connected stateor that a wireless device lastly performed an RNA update procedure in.In an example, an RNA may comprise one or more cells operated by one ormore base stations. In an example, a base station may belong to one ormore RNAs. In an example, a cell may belong to one or more RNAs.

In an example, a wireless device may transition a UE RRC state from anRRC connected state to an RRC inactive state in a base station. Awireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

In an example, an anchor base station may broadcast a message (e.g. RANpaging message) to base stations of an RNA to reach to a wireless devicein an RRC inactive state, and/or the base stations receiving the messagefrom the anchor base station may broadcast and/or multicast anothermessage (e.g. paging message) to wireless devices in their coveragearea, cell coverage area, and/or beam coverage area associated with theRNA through an air interface.

In an example, when a wireless device in an RRC inactive state movesinto a new RNA, the wireless device may perform an RNA update (RNAU)procedure, which may comprise a random access procedure by the wirelessdevice and/or a UE context retrieve procedure. A UE context retrieve maycomprise: receiving, by a base station from a wireless device, a randomaccess preamble; and fetching, by a base station, a UE context of thewireless device from an old anchor base station. Fetching may comprise:sending a retrieve UE context request message comprising a resumeidentifier to the old anchor base station and receiving a retrieve UEcontext response message comprising the UE context of the wirelessdevice from the old anchor base station.

In an example embodiment, a wireless device in an RRC inactive state mayselect a cell to camp on based on at least a on measurement results forone or more cells, a cell where a wireless device may monitor an RNApaging message and/or a core network paging message from a base station.In an example, a wireless device in an RRC inactive state may select acell to perform a random access procedure to resume an RRC connectionand/or to transmit one or more packets to a base station (e.g. to anetwork). In an example, if a cell selected belongs to a different RNAfrom an RNA for a wireless device in an RRC inactive state, the wirelessdevice may initiate a random access procedure to perform an RNA updateprocedure. In an example, if a wireless device in an RRC inactive statehas one or more packets, in a buffer, to transmit to a network, thewireless device may initiate a random access procedure to transmit oneor more packets to a base station of a cell that the wireless deviceselects. A random access procedure may be performed with two messages(e.g. 2 stage random access) and/or four messages (e.g. 4 stage randomaccess) between the wireless device and the base station.

In an example embodiment, a base station receiving one or more uplinkpackets from a wireless device in an RRC inactive state may fetch a UEcontext of a wireless device by transmitting a retrieve UE contextrequest message for the wireless device to an anchor base station of thewireless device based on at least one of an AS context identifier, anRNA identifier, a base station identifier, a resume identifier, and/or acell identifier received from the wireless device. In response tofetching a UE context, a base station may transmit a path switch requestfor a wireless device to a core network entity (e.g. AMF, MME, and/orthe like). A core network entity may update a downlink tunnel endpointidentifier for one or more bearers established for the wireless devicebetween a user plane core network entity (e.g. UPF, S-GW, and/or thelike) and a RAN node (e.g. the base station), e.g. changing a downlinktunnel endpoint identifier from an address of the anchor base station toan address of the base station.

A gNB may transmit one or more MAC PDUs to a wireless device. In anexample, a MAC PDU may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. In an example, bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. More generally, the bitstring may be read from left to right and then in the reading order ofthe lines. In an example, the bit order of a parameter field within aMAC PDU is represented with the first and most significant bit in theleftmost bit and the last and least significant bit in the rightmostbit.

In an example, a MAC SDU may be a bit string that is byte aligned (e.g.,a multiple of eight bits) in length. In an example, a MAC SDU may beincluded in a MAC PDU from the first bit onward.

In an example, a MAC CE may be a bit string that is byte aligned (e.g.,a multiple of eight bits) in length.

In an example, a MAC subheader may be a bit string that is byte aligned(e.g., a multiple of eight bits) in length. In an example, a MACsubheader may be placed immediately in front of a corresponding MAC SDU,MAC CE, or padding.

In an example, a MAC entity may ignore a value of reserved bits in a DLMAC PDU.

In an example, a MAC PDU may comprise one or more MAC subPDUs. A MACsubPDU of the one or more MAC subPDUs may comprise: a MAC subheader only(including padding); a MAC subheader and a MAC SDU; a MAC subheader anda MAC CE; and/or a MAC subheader and padding. In an example, the MAC SDUmay be of variable size. In an example, a MAC subheader may correspondto a MAC SDU, a MAC CE, or padding.

In an example, when a MAC subheader corresponds to a MAC SDU, avariable-sized MAC CE, or padding, the MAC subheader may comprise: an Rfield with a one bit length; an F field with a one bit length; an LCIDfield with a multi-bit length; and/or an L field with a multi-bitlength.

FIG. 16 shows an example of a CSI-RS that may be mapped in time andfrequency domains. Each square shown in FIG. 16 may represent a resourceblock within a bandwidth of a cell. Each resource block may comprise anumber of subcarriers. A cell may have a bandwidth comprising a numberof resource blocks. A base station (e.g., a gNB in NR) may transmit oneor more Radio Resource Control (RRC) messages comprising CSI-RS resourceconfiguration parameters for one or more CSI-RS. One or more of thefollowing parameters may be configured by higher layer signaling foreach CSI-RS resource configuration: CSI-RS resource configurationidentity, number of CSI-RS ports, CSI-RS configuration (e.g., symbol andRE locations in a subframe), CSI-RS subframe configuration (e.g.,subframe location, offset, and periodicity in a radio frame), CSI-RSpower parameter, CSI-RS sequence parameter, CDM type parameter,frequency density, transmission comb, QCL parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

FIG. 16 shows three beams that may be configured for a wireless device,e.g., in a wireless device-specific configuration. Any number ofadditional beams (e.g., represented by the column of blank squares) orfewer beams may be included. Beam 1 may be allocated with CSI-RS 1 thatmay be transmitted in some subcarriers in a resource block (RB) of afirst symbol. Beam 2 may be allocated with CSI-RS 2 that may betransmitted in some subcarriers in a RB of a second symbol. Beam 3 maybe allocated with CSI-RS 3 that may be transmitted in some subcarriersin an RB of a third symbol. All subcarriers in a RB may not necessarilybe used for transmitting a particular CSI-RS (e.g., CSI-RS 1) on anassociated beam (e.g., beam 1) for that CSI-RS. By using frequencydivision multiplexing (FDM), other subcarriers, not used for beam 1 forthe wireless device in the same RB, may be used for other CSI-RStransmissions associated with a different beam for other wirelessdevices. Additionally or alternatively, by using time domainmultiplexing (TDM), beams used for a wireless device may be configuredsuch that different beams (e.g., beam 1, beam 2, and beam 3) for thewireless device may be transmitted using some symbols different frombeams of other wireless devices.

Beam management may use a device-specific configured CSI-RS. In a beammanagement procedure, a wireless device may monitor a channel quality ofa beam pair link comprising a transmitting beam by a base station (e.g.,a gNB in NR) and a receiving beam by the wireless device (e.g., a UE).When multiple CSI-RSs associated with multiple beams are configured, awireless device may monitor multiple beam pair links between the basestation and the wireless device.

A wireless device may transmit one or more beam management reports to abase station. A beam management report may indicate one or more beampair quality parameters, comprising, e.g., one or more beamidentifications, RSRP, PMI, CQI, and/or RI, of a subset of configuredbeams.

FIG. 17 shows examples of three beam management procedures, P1, P2, andP3. Procedure P1 may be used to enable a wireless device measurement ondifferent transmit (Tx) beams of a TRP (or multiple TRPs), e.g., tosupport a selection of Tx beams and/or wireless device receive (Rx)beam(s) (shown as ovals in the top row and bottom row, respectively, ofP1). Beamforming at a TRP (or multiple TRPs) may include, e.g., anintra-TRP and/or inter-TRP Tx beam sweep from a set of different beams(shown, in the top rows of P1 and P2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Beamformingat a wireless device, may include, e.g., a wireless device Rx beam sweepfrom a set of different beams (shown, in the bottom rows of P1 and P3,as ovals rotated in a clockwise direction indicated by the dashedarrow). Procedure P2 may be used to enable a wireless device measurementon different Tx beams of a TRP (or multiple TRPs) (shown, in the top rowof P2, as ovals rotated in a counter-clockwise direction indicated bythe dashed arrow), e.g., which may change inter-TRP and/or intra-TRP Txbeam(s). Procedure P2 may be performed, e.g., on a smaller set of beamsfor beam refinement than in procedure P1. P2 may be a particular exampleof P1. Procedure P3 may be used to enable a wireless device measurementon the same Tx beam (shown as oval in P3), e.g., to change a wirelessdevice Rx beam if the wireless device uses beamforming.

FIG. 18 shows DCI formats for an example of 20 MHz FDD operation with 2Tx antennas at the base station and no carrier aggregation in an LTEsystem. In a NR system, the DCI formats may comprise at least one of:DCI format 0_0/0_1 indicating scheduling of PUSCH in a cell; DCI format1_0/1_1 indicating scheduling of PDSCH in a cell; DCI format 2_0notifying a group of UEs of slot format; DCI format 2_1 notifying agroup of UEs of PRB(s) and OFDM symbol(s) where a UE may assume notransmission is intended for the UE; DCI format 2_2 indicatingtransmission of TPC commands for PUCCH and PUSCH; and/or DCI format 2_3indicating transmission of a group of TPC commands for SRS transmissionby one or more UEs. In an example, a gNB may transmit a DCI via a PDCCHfor scheduling decision and power-control commends. More specifically,the DCI may comprise at least one of: downlink scheduling assignments,uplink scheduling grants, power-control commands. The downlinkscheduling assignments may comprise at least one of: PDSCH resourceindication, transport format, HARQ information, and control informationrelated to multiple antenna schemes, a command for power control of thePUCCH used for transmission of ACK/NACK in response to downlinkscheduling assignments. The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, a power control command of the PUSCH.

In an example, the different types of control information correspond todifferent DCI message sizes. For example, supporting spatialmultiplexing with noncontiguous allocation of RBs in the frequencydomain may require a larger scheduling message in comparison with anuplink grant allowing for frequency-contiguous allocation only. The DCImay be categorized into different DCI formats, where a formatcorresponds to a certain message size and usage.

In an example, a UE may monitor one or more PDCCH candidates to detectone or more DCI with one or more DCI format. The one or more PDCCH maybe transmitted in common search space or UE-specific search space. A UEmay monitor PDCCH with only a limited set of DCI format, to save powerconsumption. For example, a normal UE may not be required to detect aDCI with DCI format 6 which is used for an eMTC UE. The more DCI formatto be detected, the more power be consumed at the UE.

In an example, the one or more PDCCH candidates that a UE monitors maybe defined in terms of PDCCH UE-specific search spaces. A PDCCHUE-specific search space at CCE aggregation level Lϵ{1, 2, 4, 8}Lϵ{1, 2,4, 8} may be defined by a set of PDCCH candidates for CCE aggregationlevel LL. In an example, for a DCI format, a UE may be configured perserving cell by one or more higher layer parameters a number of PDCCHcandidates per CCE aggregation level LL.

In an example, in non-DRX mode operation, a UE may monitor one or morePDCCH candidate in control resource set q according to a periodicity ofW_(PDCCH, q) symbols that may be configured by one or more higher layerparameters for control resource set q.

In an example, if a UE is configured with higher layer parameter, e.g.,cif-InSchedulingCell, the carrier indicator field value may correspondto cif-InSchedulingCell.

In an example, for the serving cell on which a UE may monitor one ormore PDCCH candidate in a UE-specific search space, if the UE is notconfigured with a carrier indicator field, the UE may monitor the one ormore PDCCH candidates without carrier indicator field. In an example,for the serving cell on which a UE may monitor one or more PDCCHcandidates in a UE-specific search space, if a UE is configured with acarrier indicator field, the UE may monitor the one or more PDCCHcandidates with carrier indicator field.

In an example, a UE may not monitor one or more PDCCH candidates on asecondary cell if the UE is configured to monitor one or more PDCCHcandidates with carrier indicator field corresponding to that secondarycell in another serving cell. For example, for the serving cell on whichthe UE may monitor one or more PDCCH candidates, the UE may monitor theone or more PDCCH candidates at least for the same serving cell.

In an example, the information in the DCI formats used for downlinkscheduling may be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator (0 or 3 bits), RBallocation; HARQ process number; MCS, NDI, and RV (for the first TB);MCS, NDI and RV (for the second TB); MIMO related information; PDSCHresource-element mapping and QCI; Downlink assignment index (DAI); TPCfor PUCCH; SRS request (1 bit), triggering one-shot SRS transmission;ACK/NACK offset; DCI format 0/1A indication, used to differentiatebetween DCI format 1A and 0; and padding if necessary. The MIMO relatedinformation may comprise at least one of: PMI, precoding information,transport block swap flag, power offset between PDSCH and referencesignal, reference-signal scrambling sequence, number of layers, and/orantenna ports for the transmission.

In an example, the information in the DCI formats used for uplinkscheduling may be organized into different groups, with the fieldpresent varying between the DCI formats, including at least one of:resource information, consisting of: carrier indicator, resourceallocation type, RB allocation; MCS, NDI (for the first TB); MCS, NDI(for the second TB); phase rotation of the uplink DMRS; precodinginformation; CSI request, requesting an aperiodic CSI report; SRSrequest (2 bit), used to trigger aperiodic SRS transmission using one ofup to three preconfigured settings; uplink index/DAI; TPC for PUSCH; DCIformat 0/1A indication; and padding if necessary.

In an example, a gNB may perform CRC scrambling for a DCI, beforetransmitting the DCI via a PDCCH. The gNB may perform CRC scrambling bybit-wise addition (or Modulo-2 addition or exclusive OR (XOR) operation)of multiple bits of at least one wireless device identifier (e.g.,C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SP CSIC-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI, SI-RNTI, RA-RNTI,and/or MCS-C-RNTI) with the CRC bits of the DCI. The wireless device maycheck the CRC bits of the DCI, when detecting the DCI. The wirelessdevice may receive the DCI when the CRC is scrambled by a sequence ofbits that is the same as the at least one wireless device identifier.

In an example, as shown in FIG. 19, a wireless device (e.g., UE) mayhandover from a source base station (e.g., source gNB) to a target basestation (e.g., target gNB). For a wireless device in RRC_CONNECTEDstate, a base station may control the wireless device mobility, e.g.,the base station may decide when and where the wireless device mayinitiate a handover process. The base station may trigger the handoverprocess based on radio conditions or network load condition. The basestation may configure the wireless device to perform and reportmeasurement report (MR) (e.g., may include a configuration ofmeasurement gaps). In an example, before transmitting a handover messageto the wireless device, the source base station (e.g., source gNB) mayprepare one or more target cells (e.g., target base station). The targetbase station may generate the handover message that may be used toperform the handover process (e.g., the message may comprise a radioresource configuration to be used in the target base station). Thesource base station may transparently (e.g., the source base station maynot modify values or content of the message) forward the handovermessage received from the target base station to the wireless device(e.g., via an RRC Reconfiguration Message). The source base station mayforward data to the target base station in order to reduce the handoverinterruption time.

In an example, after receiving the handover message (e.g., via the RRCReconfiguration Message) from the source base station, the wirelessdevice may perform a random access process to access the target basestation at a first available random access channel opportunity. In anexample, when the handover process is successfully completed, thewireless device may transmit an RRC Reconfiguration Complete Message toconfirm the handover process. The wireless device may report an MR tothe target base station. The target base station may transmit a releaserequest message to the source base station according to the MR. In anexample, to eliminate latency of the random access process in thehandover process, a handover (HO) without random access process (i.e.,RACH-less HO) may be introduced. In an example, for the RACH-lesshandover, the source base station may indicate a time advance value(e.g., via the handover message) for the target base station to thewireless device. The source base station may also indicate apre-allocated uplink grant (e.g., via the handover message) for thetarget base station to the wireless device. The wireless device maytransmit an uplink transport block to the target base station based onthe time advance value and the pre-allocated uplink grant.

In an example, the RACH-less handover may be configured with one or morepre-allocated (or pre-configured) uplink grants. A wireless device maytransmit uplink transport blocks in the one or more pre-allocated (orpre-configured) uplink grants using a transmit beam. A transmit beam maybe referred to as a spatial domain transmission filter. The wirelessdevice may direct the transmit beam towards a target base station (e.g.,target gNB) based on beam correspondence (e.g., the wireless device mayobtain an uplink transmit beam according to a downlink reception beam).The target base station may not know the position of the wirelessdevice. The target base station may need to perform beam sweeping indifferent downlink beams, which may increase interruption time duringthe RACH-less handover process.

In an example, to speed up the downlink beam training, apre-configuration message for the one or more pre-allocated (orpre-configured) uplink grants during RACH-less handover may comprise anassociation relationship between multiple downlink beams (e.g., downlinkreference signals) and the one or more pre-allocated (or pre-configured)uplink grants. The target base station may include the multiple downlinkbeams information (e.g., in the form of reference signals ortransmission configuration indictors) into the RRC ReconfigurationMessage to indicate the association between the one or morepre-allocated (or pre-configured) uplink grants and SS/PBCH block(SSB)/channel state information reference signal (CSI-RS) resources. Thewireless device may select a suitable downlink beam among the multipledownlink beams to transmit a transport block with an associated uplinkgrant on PUSCH of the target base station. The target base station mayobtain downlink beam information for the wireless device after detectingthe transport block with the associated uplink grant. In an example, apower control for an uplink transport block transmission may be based ona cell specific reference signal in the existing RACH-less handoverprocess. In an example, multiple downlink beams may be supported in afuture radio system. The power control for a multiple beam radio systemmay be inefficient and inaccurate with the cell specific referencesignal. In the following, several embodiments are disclosed that mayimprove wireless device power control efficiency and accuracy for amultiple beam radio system when wireless device mobility is supported bya RACH-less handover process (or handover procedure).

FIG. 20A and FIG. 20B illustrate example embodiments of uplink transportblock transmission and retransmission via a physical uplink sharedchannel (PUSCH) for a RACH-less handover process (or handoverprocedure). In an example, a source base station (e.g., source gNB orsource cell) may configure multiple power control parameter sets (PCPSs)for a wireless device via RRC message(s) (e.g., via an RRCReconfiguration message). The multiple PCPSs may be generated by atarget base station (e.g., target gNB or target cell). The target gNBmay transmit the multiple PCPSs information to the source gNB (e.g., viaXn interface). The wireless device may use the multiple PCPSs as powercontrol parameter reference sets for determination of uplinktransmission power. The multiple PCPSs may comprise PCPS 0, PCPS 1, PCPS2, . . . , PCPS N. In an example, N may be an integer being equal to orgreater than 0. In an example, each of the multiple PCPSs may compriseone or more power control parameters (e.g., pathloss reference signalidentification, alpha set identification, and/or closed loop powercontrol index). In an example, different PCPSs of the multiple PCPSs maycomprise same values of the one or more power control parameters. In anexample, different PCPSs of the multiple PCPSs may comprise differentvalues of the one or more power control parameters.

The source base station (e.g., source gNB or source cell) may configuremultiple downlink reference signals for the wireless device via RRCmessage(s) (e.g. via an RRC Reconfiguration message). The multipledownlink reference signals may be downlink reference signals of thetarget base station (e.g., target gNB or target cell). The target gNBmay transmit the multiple downlink reference signals information to thesource gNB (e.g., via Xn interface). The wireless device may use themultiple downlink reference signals for determination of uplinktransmission power for the PUSCH of the target base station (e.g.,target gNB or target cell). The multiple downlink reference signals(RSs) may comprise RS 0, RS 1, RS 2, . . . , RS M. In an example, M maybe an integer being equal to or greater than 0. In an example, M may beequal to the N, where N is the number PCPSs. The multiple downlink RSsmay comprise SS\PBCH blocks (SSBs) and/or channel state informationreference signals (CSI-RSs). The source base station may configure anassociation relationship between the multiple downlink RSs and themultiple PCPSs to the wireless device via RRC message(s) (e.g., via theRRC Reconfiguration message). The association relationship may be a oneto one mapping relationship between the multiple downlink RSs and themultiple PCPSs. In an example, an RS of the multiple downlink RSs may beassociated with a PCPS of the multiple PCPSs. The wireless device maycalculate (or determine), based on power control parameters of the PCPS,an uplink transmission power in response to determining (or selecting)the RS based on a radio channel quality measurement.

In an example, as shown in FIG. 20A, the wireless device may transmitand/or retransmit a transport block using multiple pre-allocated (orpre-configured) uplink grants on a PUSCH of the target gNB (or targetcell). The wireless device may perform an initial transmission for thetransport block at time T1 using a pre-allocated (or pre-configured)uplink grant. The wireless device may perform a first retransmission forthe transport block at time T2 using a pre-allocated (or pre-configured)uplink grant. The wireless device may perform a second retransmissionfor the transport block at time T3 using a pre-allocated (orpre-configured) uplink grant. The wireless device may determine (orselect) different downlink beams (or different downlink RSs) asreferences for beam correspondence at time T1, T2 and T3. The wirelessdevice may determine (or select) a same downlink beam (or a samedownlink RS) as a reference for beam correspondence at time T1, T2 andT3. The wireless device may determine (or select) a downlink RS based ona radio link quality measurement (e.g., reference signal received power(RSRP) or signal to interference plus noise ratio (SINR) measurement) ofthe downlink RS. The wireless device may determine, based onmeasurements (e.g., radio link quality measurement, such as RSRP orSINR) of the multiple downlink RSs, a downlink RS of the multipledownlink RSs. The wireless device may determine (or select) the downlinkRS (or a downlink beam) with a best (e.g., highest) RSRP or SINR valuein the multiple downlink RSs (or multiple downlink beams). In anexample, a downlink reference signal may be referred to as a downlinkbeam. The wireless device may determine a PCPS from the multiple PCPSsaccording to (or based on) the association between the PCPS and thedetermined (or selected) downlink RS. The wireless device may calculate(or determine), based on the PCPS, an uplink transmission power for thePUSCH of the target base station (or target cell). The wireless devicemay transmit, with the uplink transmission power, an uplink transportblock via the PUSCH of the target base station (e.g., target gNB ortarget cell). The wireless device may retransmit the uplink transportblock via the PUSCH of the target base station. The source base station(or target base station) may configure a maximum transmission time value(e.g., comprising transmission and retransmissions) to the wirelessdevice via RRC message(s). The wireless device may stop the uplinktransport block retransmission in response to receiving acknowledgeinformation (e.g., acknowledge (ACK) or new data indicator indicating anew data). The wireless device may stop the uplink transport blocktransmission (or retransmission) in response to reaching the maximumtransmission time value.

In an example, a PCPS may comprise a pathloss reference signalidentification q_(d), an alpha set identification, and/or a closed looppower control index 1. The alpha set identified by the alpha setidentification may comprise an alpha value α_(b,f,c) and a receivedtarget power value P_(O_UE_PUSCH,b,f,c). In an example, suffix indexesb, f, and c may be bandwidth part identification, carrieridentification, and cell identification, respectively. The source basestation (or target base station) may configure a nominal received targetpower value P_(O_NOMINAL_PUSCH,f,c) to the wireless device. In anexample, P_(CMAX,f,c) may be a maximum power value in carrier f and cellc. In an example, Ω_(b,f,c) may be a value determined by a pre-allocateduplink grant. In an example, PL_(b,f,c)(q_(d)) may be a pathloss valueassociated with a pathloss reference signal identification q_(d). In anexample, Δ_(TF,b,f,c) may be determined by a modulation and codingscheme of the pre-allocated uplink grant. In an example, f_(b,f,c) maybe a closed loop power control parameter. In an example, f_(b,f,c) maybe equal to zero for an initial transmission of an uplink transportblock on a PUSCH in a RACH-less handover process. In an example,f_(b,f,c) may be equal to zero for a retransmission of the uplinktransport block on the PUSCH in the RACH-less handover process inresponse to not receiving a dynamic uplink grant. The wireless devicemay calculate (or determine) an uplink transmission power according tothe below equation based on the PCPS determined by the wireless device,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

The wireless device may determine, based on measurements of the multipledownlink RSs, a first downlink RS of the multiple downlink RSs at timeT1. The wireless device may calculate (or determine), based on a PCPSassociated with the first downlink RS, a first uplink transmission powerp1 for an uplink transport block via the PUSCH of the target basestation. The wireless device may determine, based on measurements of themultiple downlink RSs, a second downlink RS of the multiple downlink RSsat time T2. The wireless device may calculate (or determine), based on aPCPS associated with the second downlink RS, a second uplinktransmission power p2 for the uplink transport block via the PUSCH ofthe target base station. The wireless device may determine, based onmeasurements of the multiple downlink RSs, a third downlink RS of themultiple downlink RSs at time T3. The wireless device may calculate (ordetermine), based on a PCPS associated with the third downlink RS, athird uplink transmission power p 3 for the uplink transport block viathe PUSCH of the target base station. In an example, an uplinktransmission power p for the uplink transport block via the PUSCH attime T2 may be determined as p=p2+Δoffset in response to the seconddownlink RS being the same as the first downlink RS. In an example, anuplink transmission power p for the uplink transport block on the PUSCHat time T3 may be determined as p=p3+Δoffset in response to the thirddownlink RS being the same as the second downlink RS. The Δoffset may bea ramping power value. The source base station (or target base station)may configure the ramping power value Δoffset to the wireless device viaRRC message(s) (e.g., via the RRC Reconfiguration Message). In anexample, an uplink transmission power of a retransmission of thetransport block via the PUSCH may be equal to a calculated uplinktransmission power plus the ramping power value Δoffset, where thecalculated uplink transmission power may be calculated based on a PCPSassociated with a fourth determined downlink RS in the retransmission.The fourth determined downlink RS may be the same as a fifth determineddownlink RS in a latest transmission or retransmission before theretransmission.

In an example, as shown in FIG. 20B, the wireless device may transmitand/or retransmit a transport block using multiple pre-allocated (orpre-configured) uplink grants on a PUSCH of the target gNB or targetcell. The wireless device may perform an initial transmission for thetransport block at time T1 using a pre-allocated (or pre-configured)uplink grant. The wireless device may fail to receive a downlink controlinformation (DCI). The wireless device may receive a DCI indicating anegative acknowledge (NACK) at time T2. The wireless device may performa retransmission for the transport block at time T3 using apre-allocated (or pre-configured) uplink grant. The wireless device maydetermine (or select) different downlink beams (or different downlinkRSs) as references for beam correspondence at time T1 and T3. Thewireless device may determine (or select) a same downlink beam (or asame downlink RS) as a reference for beam correspondence at time T1 andT3. The wireless device may determine (or select) a downlink RS based ona radio link quality measurement (e.g., reference signal received power(RSRP) or signal to interference plus noise ratio (SINR) measurement) ofthe downlink RS. The wireless device may determine, based onmeasurements (e.g., radio link quality measurement, such as RSRP orSINR) of the multiple downlink RSs, a downlink RS of the multipledownlink RSs. The wireless device may determine (or select) the downlinkRS (or a downlink beam) with a best (e.g., highest) RSRP or SINR valuein the multiple downlink RSs (or multiple downlink beams). In anexample, a downlink reference signal may be referred to as a downlinkbeam. The wireless device may determine a PCPS from the multiple PCPSsaccording to (or based on) the association between the PCPS and thedownlink RS. The wireless device may calculate (or determine), based onthe PCPS, an uplink transmission power for the PUSCH of the target basestation (or target cell). The wireless device may transmit, with theuplink transmission power, an uplink transport block via the PUSCH ofthe target base station (e.g., target gNB or target cell). The wirelessdevice may retransmit the uplink transport block via the PUSCH of thetarget base station. The source base station (or the target basestation) may configure a maximum transmission times value (e.g.,comprising transmission and retransmissions) to the wireless device viaRRC message(s). The wireless device may stop the uplink transport blockretransmission in response to receiving acknowledge information (e.g.,acknowledge (ACK) or new data indicator indicating a new data). Thewireless device may count the transmission and retransmission times forthe uplink transport block. The wireless device may stop the uplinktransport block transmission (or retransmission) in response to thetransmission times reaching the maximum transmission times value. Thewireless device may calculate an uplink transmission power according tothe below equation based on the PCPS determined by the wireless device,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

The wireless device may determine, based on measurements of the multipledownlink RSs, a first downlink RS of the multiple downlink RSs at timeT1. The wireless device may calculate (or determine), according to aPCPS associated with the first downlink RS, a first uplink transmissionpower p1 for a first transmission of an uplink transport block on thePUSCH of the target base station at time T1. The wireless device maydetermine, based on measurements of the multiple downlink RSs, a seconddownlink RS of the multiple downlink RSs at time T3. The wireless devicemay calculate (or determine), according to a PCPS associated with thesecond downlink RS, a second uplink transmission power p2 for a secondtransmission of the uplink transport block on the PUSCH of the targetbase station at time T3. In an example, an uplink transmission power pfor the uplink transport block of the second transmission on the PUSCHmay be determined as p=p2+Δoffset in response to the second downlink RSbeing the same as the first downlink RS. The first uplink transmissionmay be an initial transmission of the uplink transport block. TheΔoffset may be a ramping power value. The source base station (or targetbase station) may configure the ramping power value Δoffset to thewireless device (e.g., via the RRC Reconfiguration Message). In anexample, an uplink transmission power of a retransmission of thetransport block on the PUSCH may be equal to a calculated uplinktransmission power plus the ramping power value Δoffset, where thecalculated uplink transmission power may be calculated based on a PCPSassociated with a third determined downlink RS in the retransmission andthe third determined downlink RS may be the same as a fourth determineddownlink RS in a latest transmission or retransmission before theretransmission.

In an example, FIG. 21 illustrates an example power control procedurefor a RACH-less handover process in accordance with embodiments of thepresent disclosure. In an example, a wireless device may receive one ormore RRC messages from a source base station at time T1. The one or moreRRC messages may comprise configuration parameters indicating multiplepower control parameter sets (PCPSs), and multiple downlink referencesignals (e.g., via an RRC Reconfiguration message). The multiple PCPSsmay be generated by a target base station (e.g., target gNB or targetcell). The target gNB may transmit the multiple PCPSs information to thesource gNB (e.g., via Xn interface). The wireless device may use themultiple PCPSs as power control parameter reference sets fordetermination of uplink transmission power. In an example, each of themultiple PCPSs may comprise one or more power control parameters (e.g.,power control identification, pathloss reference signal identification,alpha set identification, and/or closed loop power control index). In anexample, different PCPSs of the multiple PCPSs may comprise the samevalues of the one or more power control parameters. In an example,different PCPSs of the multiple PCPSs may comprise different values ofthe one or more power control parameters. The multiple downlinkreference signals may be downlink reference signals of the target basestation (e.g., target gNB or target cell). The target gNB may transmitthe multiple downlink reference signals information to the source gNB(e.g., via Xn interface). The wireless device may use the multipledownlink reference signals (RSs) for determination of uplinktransmission power for the PUSCH of the target base station (e.g.,target gNB or target cell). The multiple downlink RSs may compriseSS\PBCH blocks (SSBs) or channel state information reference signals(CSI-RSs). The source base station may configure an associationrelationship between the multiple downlink RSs and the multiple PCPSs tothe wireless device (e.g., via the RRC Reconfiguration message). In anexample, an RS of the multiple downlink RSs may be associated with aPCPS of the multiple PCPSs.

The wireless device may determine (or select) a downlink RS based on aradio link quality measurement (e.g., reference signal received power(RSRP) or signal to interference plus noise ratio (SINR) measurement) ofthe downlink RS at time T2. The wireless device may determine (orselect) the downlink RS (or a downlink beam) with a best (e.g., highest)RSRP or SINR value in the multiple downlink RSs (or multiple downlinkbeams). The wireless device may determine a PCPS from the multiple PCPSsaccording to an association between the PCPS and the downlink RS at timeT3. The wireless device may calculate (or determine), based on the PCPS,an uplink transmission power for the PUSCH of the target base station(or target cell) at time T4. The wireless device may transmit, with theuplink transmission power, an uplink transport block via the PUSCH ofthe target base station (e.g., target gNB or target cell) at time T5.The wireless device may retransmit the uplink transport block via thePUSCH of the target base station. The source base station (or targetbase station) may configure a maximum transmission times value (e.g.,comprising transmission and retransmissions) to the wireless device viaRRC message(s). The wireless device may stop the uplink transport blockretransmission in response to receiving acknowledge information (e.g.,acknowledge (ACK) or new data indicator indicating a new data). Thewireless device may stop the uplink transport block transmission (orretransmission) in response to the transmission times reaching themaximum transmission times value.

The wireless device may retransmit the uplink transport block with aretransmission power at time T6. The wireless device may determine,based on measurements of the multiple downlink RSs, a first downlink RSof the multiple downlink RSs. The wireless device may calculate (ordetermine) a first uplink transmission power p1 for a first transmissionof an uplink transport block on the PUSCH of the target base stationaccording to a PCPS associated with the first downlink RS. The wirelessdevice may determine, based on measurements of the multiple downlinkRSs, a second downlink RS of the multiple downlink RSs. The wirelessdevice may calculate (or determine) a second uplink transmission powerp2 for a second transmission of the uplink transport block on the PUSCHof the target base station according to a PCPS associated with thesecond downlink RS. In an example, an uplink transmission power p forthe uplink transport block of the second transmission on the PUSCH maybe determined as p=p2+Δoffset in response to the second downlink RSbeing the same as the first downlink RS. The first uplink transmissionmay be a retransmission of the uplink transport block. The first uplinktransmission may be an initial transmission of the uplink transportblock. The Δoffset may be a ramping power value. The source base station(or target base station) may configure the ramping power value Δoffsetto the wireless device via RRC message(s) (e.g., via the RRCReconfiguration Message). In an example, an uplink transmission power ofa retransmission of the transport block on the PUSCH may be equal to acalculated uplink transmission power plus the ramping power valueΔoffset, where the calculated uplink transmission power may becalculated based on a PCPS associated with a third determined downlinkRS in the retransmission and the third determined downlink RS may be thesame as a fourth determined downlink RS in a latest transmission orretransmission before the retransmission.

In an example, FIG. 22 illustrates an example of flow chart of powercontrol process in accordance with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station. The one or more RRC messages maycomprise configuration parameters indicating multiple power controlparameter sets (PCPSs) and multiple downlink reference signals (RSs)(e.g. via an RRC Reconfiguration message). The multiple PCPSs may begenerated by a target base station (e.g., target gNB or target cell).The target gNB may transmit the multiple PCPSs information to the sourcegNB (e.g., via Xn interface). The wireless device may use the multiplePCPSs as power control parameter reference sets for determination ofuplink transmission power. In an example, each of the multiple PCPSs maycomprise one or more power control parameters (e.g., power controlidentification, pathloss reference signal identification, alpha setidentification, and/or closed loop power control index). In an example,different PCPSs of the multiple PCPSs may comprise same values of theone or more power control parameters. In an example, different PCPSs ofthe multiple PCPSs may comprise different values of the one or morepower control parameters. The multiple downlink reference signals (RSs)may be downlink reference signals (RSs) of the target base station(e.g., target gNB or target cell). The target gNB may transmit themultiple downlink reference signals (RSs) information to the source gNB(e.g., via Xn interface). The wireless device may use the multipledownlink reference signals (RSs) for determination of uplinktransmission power for the PUSCH of the target base station (e.g.,target gNB or target cell). The multiple downlink RSs may compriseSS\PBCH blocks (SSBs) and/or channel state information reference signals(CSI-RSs). The source base station may configure an associationrelationship between the multiple downlink RSs and the multiple PCPSs tothe wireless device via RRC message(s) (e.g., via the RRCReconfiguration message). In an example, an RS of the multiple downlinkRSs may be associated with a PCPS of the multiple PCPSs.

The wireless device may determine (or select) a downlink RS based on aradio link quality measurement (e.g., reference signal received power(RSRP) or signal to interference plus noise ratio (SINR) measurement) ofthe downlink RS. The wireless device may determine (or select) thedownlink RS (or a downlink beam) with a best (e.g., highest) RSRP orSINR value in the multiple downlink RSs (or multiple downlink beams).The wireless device may determine a PCPS from the multiple PCPSsaccording to (or based on) an association between the PCPS and thedownlink RS. The wireless device may calculate (or determine), based onthe PCPS, an uplink transmission power for the PUSCH of the target basestation (or target cell). The wireless device may transmit, with theuplink transmission power, an uplink transport block via the PUSCH ofthe target base station (e.g., target gNB or target cell). The wirelessdevice may retransmit the uplink transport block via the PUSCH of thetarget base station. The source base station (or target base station)may configure a maximum transmission times value K (e.g., comprisingtransmission and retransmissions) to the wireless device via RRCmessage(s). The wireless device may stop the uplink transport blockretransmission in response to receiving acknowledge information (e.g.,acknowledge (ACK) or new data indicator indicating a new data). Thewireless device may stop the uplink transport block transmission (orretransmission) in response to the transmission times reaching themaximum transmission times value K.

The wireless device may retransmit the uplink transport block with aretransmission power. The wireless device may determine, based onmeasurements of the multiple downlink RSs, a first downlink RS of themultiple downlink RSs. The wireless device may calculate a first uplinktransmission power p1 for a first transmission of an uplink transportblock on the PUSCH of the target base station according to a PCPSassociated with the first downlink RS. The wireless device maydetermine, based on measurements of the multiple downlink RSs, a seconddownlink RS of the multiple downlink RSs. The wireless device maycalculate a second uplink transmission power p2 for a secondtransmission of the uplink transport block on the PUSCH of the targetbase station according to a PCPS associated with the second downlink RS.In an example, an uplink transmission power p for the uplink transportblock of the second transmission on the PUSCH may be determined asp=p2+Δoffset in response to the second downlink RS being the same as thefirst downlink RS. The first uplink transmission may be a retransmissionof the uplink transport block. The first uplink transmission may be aninitial transmission of the uplink transport block. The Δoffset may be aramping power value. The source base station (or target base station)may configure the ramping power value Δoffset to the wireless device viaRRC message(s) (e.g., via the RRC Reconfiguration Message). In anexample, an uplink transmission power of a retransmission of thetransport block on the PUSCH may be equal to a calculated uplinktransmission power plus the ramping power value Δoffset. The calculateduplink transmission power may be calculated based on a PCPS associatedwith a third determined downlink RS in the retransmission. The thirddetermined downlink RS may be the same as a fourth determined downlinkRS in a latest transmission (or retransmission) before theretransmission.

In an example, a wireless device may receive, from a first cell, one ormore messages comprising configuration parameters of a second cell. Theconfiguration parameters may indicate: a plurality of power controlparameter sets (PCPSs), and a plurality of downlink reference signals.The wireless device may determine, based on measurements of theplurality of downlink reference signals, a downlink reference signal ofthe plurality of downlink reference signals. The wireless device maydetermine a PCPS, from the plurality of PCPSs, that is associated withthe downlink reference signal. The wireless device may calculate (ordetermine), based on the PCPS, an uplink transmission power for aphysical uplink shared channel (PUSCH) of the second cell. The wirelessdevice may transmit, with the uplink transmission power, an uplinktransport block via the PUSCH of the second cell. The wireless devicemay calculate (or determine), based on the uplink transmission power anda ramping power value, a second uplink transmission power for the PUSCHof the second cell. The wireless device may retransmit, with the seconduplink transmission power, the uplink transport block on the PUSCH ofthe second cell. The wireless device may determine, based onmeasurements of the plurality of downlink reference signals, a seconddownlink reference signal of the plurality of downlink referencesignals. The wireless device may determine a second PCPS, from theplurality of PCPSs, that is associated with the second downlinkreference signal. The wireless device may calculate (or determine),based on the second PCPS, a third uplink transmission power for thePUSCH of the second cell. The wireless device may retransmit, with thethird uplink transmission power, the uplink transport block on the PUSCHof the second cell. In an example, radio resources of the PUSCH may beconfigured by a radio resource control (RRC) reconfiguration message.The measurement may comprise measurement of reference signal receivedpower (RSRP) or signal to interference plus noise ratio (SINR). Thepower control parameter set (PCPS) may comprise at least one of powercontrol parameters of pathloss reference signal identification, alphaset identification, and closed loop power control index. The first cellmay be a source cell (or source base station or source gNB). The secondcell may be a target cell (or target base station or target gNB). Theplurality of downlink reference signals may comprise SS/PBCH blocks(SSBs) and/or channel state information reference signals (CSI-RSs). Thedetermining the downlink reference signal may comprise determining thedownlink reference signal with the best radio link quality of RSRP orSINR. The determining the PCPS, from the plurality of PCPSs, that isassociated with the downlink reference signal may comprise selecting thePCPS having a one to one mapping relationship with the downlinkreference signal. The determining the second PCPS, from the plurality ofPCPSs, that is associated with the second downlink reference signal maycomprise selecting the second PCPS having a one to one mappingrelationship with the second downlink reference signal. The calculating,based on the PCPS, the uplink transmission power may comprise taking thePCPS as input of calculating equations for the uplink transmissionpower. The calculating, based on the second PCPS, the third uplinktransmission power may comprise taking the second PCPS as input ofcalculating equations for the third uplink transmission power.

FIG. 23A illustrates an example embodiment of uplink transport blocktransmission (or retransmission) via physical uplink shared channel(PUSCH) for a RACH-less handover process. In an example, a source basestation (e.g., source gNB or source cell) may configure multiple powercontrol parameter sets (PCPSs) for a wireless device via RRC message(s)(e.g. via an RRC Reconfiguration message). The multiple PCPSs may begenerated by a target base station (e.g., target gNB or target cell).The target gNB may transmit the multiple PCPSs information to the sourcegNB (e.g., via Xn interface). The wireless device may use the multiplePCPSs as power control parameter reference sets for determination ofuplink transmission power. The multiple PCPSs may comprise PCPS 0, PCPS1, PCPS 2, . . . , PCPS N. In an example, N may be an integer beingequal to or greater than 0. In an example, each of the multiple PCPSsmay comprise one or more power control parameters (e.g., pathlossreference signal identification, alpha set identification, and/or closedloop power control index). In an example, different PCPSs of themultiple PCPSs may comprise same values of the one or more power controlparameters. In an example, different PCPSs of the multiple PCPSs maycomprise different values of the one or more power control parameters.

The source base station (e.g., source gNB or source cell) may configuremultiple downlink reference signals for the wireless device via RRCmessage(s) (e.g. via an RRC Reconfiguration message). The multipledownlink reference signals may be downlink reference signals of thetarget base station (e.g., target gNB or target cell). The target gNBmay transmit the multiple downlink reference signals information to thesource gNB (e.g., via Xn interface). The wireless device may use themultiple downlink reference signals for determination of uplinktransmission power for the PUSCH. The multiple downlink referencesignals (RSs) may comprise RS 0, RS 1, RS 2, . . . , RS M. In anexample, M may be an integer being equal to or greater than 0. In anexample, M may be equal to N. The multiple downlink RSs may compriseSS\PBCH blocks (SSBs) and/or channel state information reference signals(CSI-RSs). The source base station may configure an associationrelationship between the multiple downlink RSs and the multiple PCPSs tothe wireless device via RRC message(s) (e.g., via the RRCReconfiguration message). The association relationship may be a one toone mapping relationship. In an example, an RS of the multiple downlinkRSs may be associated with a PCPS of the multiple PCPSs. The wirelessdevice may calculate (or determine), based on power control parametersof the PCPS, an uplink transmission power in response to determining (orselecting) the RS based on a radio channel quality measurement.

The wireless device may transmit and/or retransmit a transport blockusing multiple pre-allocated (or pre-configured) uplink grants on aPUSCH of the target gNB (or target cell). The wireless device mayperform a transmission (e.g., initial transmission or a retransmission)for the transport block at time T1 using a pre-allocated (orpre-configured) uplink grant. The wireless device may receive a downlinkcontrol information (DCI) with a negative acknowledge (NACK) at time T2.The wireless device may perform a retransmission for the transport blockat time T3 with an uplink grant indicated in the DCI. The wirelessdevice may determine (or select) different downlink beams (or differentdownlink RSs) as references for beam correspondence at time T1 and T3.The wireless device may determine (or select) a same downlink beam (or asame downlink RS) as a reference for beam correspondence at time T1 andT3. The wireless device may determine (or select) a downlink RS based ona radio link quality measurement (e.g., reference signal received power(RSRP) or signal to interference plus noise ratio (SINR) measurement) ofthe downlink RS. The wireless device may determine, based onmeasurements (e.g., radio link quality measurement, such as RSRP orSINR) of the multiple downlink RSs, a downlink RS of the multipledownlink RSs. The wireless device may determine (or select) the downlinkRS (or a downlink beam) with a best (e.g., highest) RSRP or SINR valuein the multiple downlink RSs (or multiple downlink beams). In anexample, a downlink reference signal may be referred to as a downlinkbeam. The wireless device may determine a PCPS from the multiple PCPSsaccording to the association between the PCPS and the downlink RS. Thewireless device may calculate (or determine), based on the PCPS and theDCI, an uplink transmission power for the PUSCH of the target basestation (or target cell). The wireless device may transmit, with theuplink transmission power, an uplink transport block via the PUSCH ofthe target base station (e.g., target gNB or target cell). The wirelessdevice may retransmit the uplink transport block via the PUSCH of thetarget base station.

In an example, a PCPS may comprise pathloss reference signalidentification q_(d), alpha set identification, and/or closed loop powercontrol index 1. The alpha set may comprise an alpha value α_(b,f,c) anda received target power value P_(O_UE_PUSCH,b,f,c). In an example,suffix indexes b, f, and c may be bandwidth part identification, carrieridentification and cell identification, respectively. The source basestation (or target base station) may configure a nominal received targetpower value P_(O_NOMINAL_PUSCH,f,c) to the wireless device. In anexample, P_(CMAX,f,c) may be a maximum power value in carrier f and cellc. In an example, Ω_(b,f,c) may be a value determined by a pre-allocateduplink grant. In an example, PL_(b,f,c)(q_(d)) may be a pathloss valueassociated with a pathloss reference signal identification q_(d). In anexample, Δ_(TF,b,f,c) may be determined by a modulation coding scheme ofthe pre-allocated uplink grant. In an example, f_(b,f,c) may be a closeloop power control parameter. In an example, f_(b,f,c) may be set to bezero in response to not receiving a dynamic uplink grant before atransmission (or retransmission). The wireless device may calculate anuplink transmission power according to the below equations based on thePCPS determined by the wireless device,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

The wireless device may determine, based on measurements of the multipledownlink RSs, a first downlink RS of the multiple downlink RSs at timeT1. The wireless device may calculate (or determine), according to aPCPS associated with the first downlink RS, a first uplink transmissionpower p1 for an uplink transport block via the PUSCH of the target basestation (e.g., not receiving a dynamic uplink grant before the firstuplink transmission). The wireless device may receive a downlink controlinformation (DCI) indicating a NACK at time T2. The DCI may comprise atransmit power control (TPC) command. The DCI may comprise an uplinkgrant. The wireless device may determine, based on measurements of themultiple downlink RSs, a second downlink RS of the multiple downlink RSsat time T3. The wireless device may calculate (or determine), accordingto a PCPS (e.g., associated with the second downlink RS) and a TPCcommand in the DCI, a second uplink transmission power p2 for the uplinktransport block on the PUSCH of the target base station. The wirelessdevice may calculate the second uplink transmission power p2 using thebelow equations,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

In an example, as shown in FIG. 23B, the wireless device may transmitand/or retransmit a transport block on a PUSCH of the target gNB (ortarget cell). The wireless device may perform a transmission (or aretransmission) for the transport block using a pre-allocated (orpre-configured) uplink grant. The wireless device may receive a downlinkcontrol information (DCI) indicating a negative acknowledge (NACK). TheDCI may comprise an uplink grant. The uplink grant may comprise a TPCcommand. The wireless device may determine (or select) a downlink RSbased on a radio link quality measurement (e.g., reference signalreceived power (RSRP) or signal to interference plus noise ratio (SINR)measurement) of the downlink RS. The wireless device may determine,based on measurements (e.g., radio link quality measurement, such asRSRP or SINR) of the multiple downlink RSs, a downlink RS of themultiple downlink RSs. The wireless device may determine (or select) thedownlink RS (or a downlink beam) with a best (e.g., highest) RSRP orSINR value in the multiple downlink RSs (or multiple downlink beams).The wireless device may determine a PCPS from the multiple PCPSsaccording to the association between the PCPS and the downlink RS. Thewireless device may calculate (or determine), based on the PCPS and theTPC command indicated by the DCI, an uplink transmission power for thePUSCH of the target base station (or target cell). The wireless devicemay transmit, with the uplink transmission power, an uplink transportblock on the PUSCH of the target base station (e.g., target gNB ortarget cell).

In an example, FIG. 24 illustrates an example of power control procedurefor RACH-less handover process with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station at time T1. The one or more RRCmessages may comprise configuration parameters indicating multiple powercontrol parameter sets (PCPSs) and multiple downlink reference signals(e.g. via an RRC Reconfiguration message). The multiple PCPSs may begenerated by a target base station (e.g., target gNB or target cell).The target gNB may transmit the multiple PCPSs information to the sourcegNB (e.g., via Xn interface). The wireless device may use the multiplePCPSs as power control parameter reference sets for determination ofuplink transmission power. In an example, each of the multiple PCPSs maycomprise one or more power control parameters (e.g., power controlidentification, pathloss reference signal identification, alpha setidentification, and/or closed loop power control index). In an example,different PCPSs of the multiple PCPSs may comprise same values of theone or more power control parameters. In an example, different PCPSs ofthe multiple PCPSs may comprise different values of the one or morepower control parameters. The multiple downlink reference signals may bedownlink reference signals of the target base station (e.g., target gNBor target cell). The target gNB may transmit the multiple downlinkreference signals information to the source gNB (e.g., via Xninterface). The wireless device may use the multiple downlink referencesignals for determination of uplink transmission power for the PUSCH.The multiple downlink RSs may comprise SS\PBCH blocks (SSBs) or channelstate information reference signals (CSI-RSs). The source base stationmay configure an association relationship between the multiple downlinkRSs and the multiple PCPSs to the wireless device via RRC message(s)(e.g., via the RRC Reconfiguration message). In an example, an RS of themultiple downlink RSs may be associated with a PCPS of the multiplePCPSs.

The wireless device may transmit (or retransmit) an uplink transportblock at time T2. The wireless device may receive a downlink controlinformation (DCI) indicating a NACK at time T3. The DCI may comprise anuplink grant. The uplink grant may comprise a transmit power control(TPC) command. The wireless device may determine (or select) a downlinkRS based on a radio link quality measurement (e.g., reference signalreceived power (RSRP) or signal to interference plus noise ratio (SINR)measurement) of the downlink RS at time T4. The wireless device maydetermine (or select) the downlink RS (or a downlink beam) with a best(e.g., highest) RSRP or SINR value in the multiple downlink RSs (ormultiple downlink beams). The wireless device may determine a PCPS fromthe multiple PCPSs according to an association between the PCPS and thedownlink RS at time T5. The association may be a one to one mappingrelationship. The wireless device may calculate (or determine), based onthe PCPS and the TPC command indicated by the DCI, an uplinktransmission power for the PUSCH of the target base station (or targetcell) at time T6. The wireless device may retransmit, with the uplinktransmission power, the uplink transport block on the PUSCH of thetarget base station (e.g., target gNB or target cell) at time T7.

In an example, FIG. 25 illustrates an example of flow chart of powercontrol process in accordance with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station. The one or more RRC messages maycomprise configuration parameters indicating multiple power controlparameter sets (PCPSs) and multiple downlink reference signals (e.g. viaan RRC Reconfiguration message). The multiple PCPSs may be generated bya target base station (e.g., target gNB or target cell). The target gNBmay transmit the multiple PCPSs information to the source gNB (e.g., viaXn interface). The wireless device may use the multiple PCPSs as powercontrol parameter reference sets for determination of uplinktransmission power. In an example, each of the multiple PCPSs maycomprise one or more power control parameters (e.g., power controlidentification, pathloss reference signal identification, alpha setidentification, and/or closed loop power control index). In an example,different PCPSs of the multiple PCPSs may comprise same values of theone or more power control parameters. In an example, different PCPSs ofthe multiple PCPSs may comprise different values of the one or morepower control parameters. The multiple downlink reference signals may bedownlink reference signals of the target base station (e.g., target gNBor target cell). The target gNB may transmit the multiple downlinkreference signals information to the source gNB (e.g., via Xninterface). The wireless device may use the multiple downlink referencesignals for determination of uplink transmission power for the PUSCH.

The multiple downlink RSs may comprise SS\PBCH blocks (SSBs) and\orchannel state information reference signals (CSI-RSs). The source basestation may configure an association relationship between the multipledownlink RSs and the multiple PCPSs to the wireless device via RRCmessage(s) (e.g., via the RRC Reconfiguration message). The associationrelationship may be a one to one mapping relationship. In an example, anRS of the multiple downlink RSs may be associated with a PCPS of themultiple PCPSs. The wireless device may transmit (or retransmit) anuplink transport block. The wireless device may receive a downlinkcontrol information (DCI) indicating a NACK. The DCI may comprise anuplink grant. The uplink grant may comprise a transmit power control(TPC) command. The wireless device may determine (or select) a downlinkRS based on a radio link quality measurement (e.g., reference signalreceived power (RSRP) or signal to interference plus noise ratio (SINR)measurement) of the downlink RS. The wireless device may determine (orselect) the downlink RS (or a downlink beam) with a best (e.g., highest)RSRP or SINR value in the multiple downlink RSs (or multiple downlinkbeams). The wireless device may determine a PCPS from the multiple PCPSsbased on an association between the PCPS and the downlink RS. Thewireless device may calculate (or determine), based on the PCPS and theDCI, an uplink transmission power for the PUSCH of the target basestation (or target cell). The wireless device may retransmit, with theuplink transmission power, an uplink transport block on the PUSCH of thetarget base station (e.g., target gNB or target cell).

In an example, a wireless device may receive, from a first cell, one ormore messages comprising configuration parameters of a second cell. Theconfiguration parameters may indicate: a plurality of power controlparameter sets (PCPSs), and a plurality of downlink reference signals.The wireless device may receive, from the second cell, a downlinkcontrol information (DCI) indicating a negative acknowledgement (NACK)in response to a transmission of an uplink transport block to the secondcell. The wireless device may determine, based on measurements of theplurality of downlink reference signals, a downlink reference signal ofthe plurality of downlink reference signals. The wireless device maydetermine a PCPS, from the plurality of PCPSs, that is associated withthe downlink reference signal. The wireless device may calculate (ordetermine), based on the PCPS and a transmit power control (TPC) commandindicated by the DCI, an uplink transmission power for a physical uplinkshared channel (PUSCH) of the second cell. The wireless device maytransmit, with the uplink transmission power, the uplink transport blockon the PUSCH of the second cell. The transmission of the uplinktransport block to the second cell may comprise initial transmission orretransmission of the uplink transport block to the second cell. Themeasurement may comprise measurement of reference signal received power(RSRP) or signal to interference plus noise ratio (SINR). The powercontrol parameter set (PCPS) may comprise at least one of: power controlparameters of pathloss reference signal identification, alpha setidentification, and closed loop power control index. The first cell maybe a source cell or a source base station, and the second cell may be atarget cell or a target base station. The plurality of downlinkreference signals may comprise SS/PBCH blocks (SSBs) and/or channelstate information reference signals (CSI-RSs). The determining thedownlink reference signal may comprise determining the downlinkreference signal with the best radio link quality of RSRP or SINR. Thedetermining the PCPS, from the plurality of PCPSs, that is associatedwith the downlink reference signal may comprise selecting the PCPShaving a one to one mapping relationship with the downlink referencesignal. The calculating, based on the PCPS and transmit power control(TPC) command indicated by the DCI, the uplink transmission power maycomprise taking the PCPS and transmit power control (TPC) command asinput of calculating equations for the uplink transmission power.

FIG. 26 illustrates an example embodiment of uplink transport blocktransmission (or retransmission) on physical uplink shared channel(PUSCH) for a RACH-less handover process. In an example, a source basestation (e.g., source gNB or source cell) may configure multiple powercontrol parameter sets (PCPSs) for a wireless device via RRC message(s)(e.g. via an RRC Reconfiguration message). The multiple PCPSs may begenerated by a target base station (e.g., target gNB or target cell).The target gNB may transmit the multiple PCPSs information to the sourcegNB (e.g., via Xn interface). The wireless device may use the multiplePCPSs as power control parameter reference sets for determination ofuplink transmission power. The multiple PCPSs may comprise PCPS 0, PCPS1, PCPS 2, . . . , PCPS N. In an example, N may be an integer beingequal to or greater than 0. In an example, each of the multiple PCPSsmay comprise one or more power control parameters (e.g., pathlossreference signal identification, alpha set identification, and/or closedloop power control index). In an example, different PCPSs of themultiple PCPSs may comprise same values of the one or more power controlparameters. In an example, different PCPSs of the multiple PCPSs maycomprise different values of the one or more power control parameters.

The source base station (e.g., source gNB or source cell) may configuremultiple downlink reference signals for the wireless device (e.g. via anRRC Reconfiguration message). The multiple downlink reference signalsmay be downlink reference signals of the target base station (e.g.,target gNB or target cell). The target gNB may transmit the multipledownlink reference signals information to the source gNB (e.g., via Xninterface). The wireless device may use the multiple downlink referencesignals for determination of an uplink transmission power for the PUSCH.The multiple downlink reference signals (RSs) may comprise RS 0, RS 1,RS 2, . . . , RS M. In an example, M may be an integer being equal to orgreater than 0. In an example, M may be equal to N. The multipledownlink RSs may comprise SS\PBCH blocks (SSBs) or channel stateinformation reference signals (CSI-RSs). The source base station mayconfigure an association relationship between the multiple downlink RSsand the multiple PCPSs to the wireless device via RRC message(s) (e.g.,via the RRC Reconfiguration message). The association relationship maybe a one to one mapping relationship. In an example, an RS of themultiple downlink RSs may be associated with a PCPS of the multiplePCPSs. The wireless device may calculate (or determine), based on powercontrol parameters of the PCPS, an uplink transmission power in responseto determining (or selecting) the RS based on a radio channel qualitymeasurement. The source base station may configure a counter and acounter threshold value to the wireless device via RRC message(s) (e.g.via the RRC Reconfiguration message).

The wireless device may transmit and/or retransmit a transport blockusing multiple pre-allocated (or pre-configured) uplink grants on aPUSCH of the target gNB (or target cell). The wireless device mayperform a transmission (e.g., initial transmission or a retransmission)for the transport block at time T1 (e.g., using a pre-allocated uplinkgrant for initial transmission or dynamic uplink grant forretransmission). The wireless device may reset the counter at time T1.The wireless device may receive a downlink control information (DCI)indicating a negative acknowledge (NACK) at time T2. The wireless devicemay perform a retransmission for the transport block at time T3 with anuplink grant indicated by the DCI. The wireless device may determine (orselect) different downlink beams (or different downlink RSs) asreferences for beam correspondence at time T1 and T3. The wirelessdevice may determine (or select) a same downlink beam (or a samedownlink RS) as a reference for beam correspondence at time T1 and T3.The wireless device may determine (or select) a downlink RS based on aradio link quality measurement (e.g., reference signal received power(RSRP) or signal to interference plus noise ratio (SINR) measurement) ofthe downlink RS. The wireless device may determine, based onmeasurements (e.g., radio link quality measurement, such as RSRP orSINR) of the multiple downlink RSs, a downlink RS of the multipledownlink RSs. The wireless device may determine (or select) the downlinkRS (or a downlink beam) with a best (e.g., highest) RSRP or SINR valuein the multiple downlink RSs (or multiple downlink beams). In anexample, a downlink reference signal may be referred to as a downlinkbeam. The wireless device may determine a PCPS from the multiple PCPSsbased on the association between the PCPS and the downlink RS. Thewireless device may calculate (or determine), based on the PCPS, anuplink transmission power for the PUSCH of the target base station (ortarget cell) (e.g., not receiving a dynamic uplink grant from a basestation). The wireless device may transmit, with the uplink transmissionpower, an uplink transport block via the PUSCH of the target basestation (e.g., target gNB or target cell). The wireless device mayretransmit the uplink transport block on the PUSCH of the target basestation.

In an example, a PCPS may comprise pathloss reference signalidentification q_(d), alpha set identification, and/or closed loop powercontrol index 1. The alpha set may comprise an alpha value α_(b,f,c) anda received target power value P_(O_UE_PUSCH,b,f,c). In an example,suffix indexes b, f, and c may be bandwidth part identification, carrieridentification and cell identification, respectively. The source basestation (or target base station) may configure a nominal received targetpower value P_(O_NOMINAL_PUSCH,f,c) to the wireless device. In anexample, P_(CMAX,f,c) may be a maximum power value in carrier f and cellc. In an example, Ω_(b,f,c) may be a value determined by a pre-allocateduplink grant. In an example, PL_(b,f,c)(q_(d)) may be a pathloss valueassociated with a pathloss reference signal identification q_(d). In anexample, Δ_(TF,b,f,c) may be determined by a modulation coding scheme ofthe pre-allocated uplink grant. In an example, f_(b,f,c) may be a closeloop power control parameter. In an example, f_(b,f,c) may be set to bezero in response to not receiving a dynamic uplink grant before atransmission (or retransmission). The wireless device may calculate anuplink transmission power according to the below equations based on thePCPS determined by the wireless device,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

The wireless device may determine, based on measurements of the multipledownlink RSs, a first downlink RS of the multiple downlink RSs at timeT1. The wireless device may calculate, according to a PCPS associatedwith the first downlink RS, a first uplink transmission power p1 for anuplink transport block on the PUSCH of the target base station (e.g.,not receiving a dynamic uplink grant before the first uplinktransmission). The wireless device may receive a downlink controlinformation (DCI) indicating a NACK at time T2. The DCI may comprise atransmit power control (TPC) command. The DCI may comprise an uplinkgrant. The wireless device may determine, based on measurements of themultiple downlink RSs, a second downlink RS of the multiple downlink RSsat time T3. The wireless device may calculate, according to a PCPS(associated with the second downlink RS) and a TPC command in the DCI, asecond uplink transmission power p2 for the uplink transport block onthe PUSCH of the target base station. The wireless device may calculatethe second uplink transmission power p2 using the below equations,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

In an example, a wireless device may perform an initial transmission fora transport block using a pre-allocated (or pre-configured) uplinkgrant. The wireless device may receive a downlink control information(DCI) indicating a negative acknowledge (NACK). The DCI may comprise anuplink grant. The uplink grant may comprise a TPC command. The wirelessdevice may determine (or select) a downlink RS based on a radio linkquality measurement (e.g., reference signal received power (RSRP) orsignal to interference plus noise ratio (SINR) measurement) of thedownlink RS. The wireless device may determine, based on measurements(e.g., radio link quality measurement, such as RSRP or SINR) of themultiple downlink RSs, a downlink RS of the multiple downlink RSs. Thewireless device may determine (or select) the downlink RS (or a downlinkbeam) with a best (e.g., highest) RSRP or SINR value in the multipledownlink RSs (or multiple downlink beams). The wireless device maydetermine a PCPS from the multiple PCPSs according to the associationbetween the PCPS and the downlink RS. The wireless device may calculate(or determine), based on the PCPS and the TPC command indicated by theDCI, an uplink transmission power for a retransmission in response tothe NACK. The wireless device may retransmit, with the uplinktransmission power, the uplink transport block on the PUSCH of thetarget base station (e.g., target gNB or target cell). The wirelessdevice may increment the counter with a step size in response to theretransmission. The wireless device may increment the counter with astep size in response to the DCI indicating the NACK. The step size maybe equal to 1. The step size may be a configured value by a base stationvia RRC message(s). The wireless device may switch (or fall back) to arandom access procedure in response to the counter value being greaterthan a counter threshold value. The wireless device may calculate (ordetermine) an uplink transmission power for a preamble based on a latestDCI with a transmit power control (TPC) command. The wireless device maycalculate (or determine) an uplink transmission power for the preamblewith a power ramping value Δ. The power ramping value Δ may beconfigured to the wireless device via an RRC message. The uplinktransmission power for the preamble may be determined as the belowequations, P_(PRACH,b,f,c)=min{P_(CMAX,f,c),P_(PRACH,target,f,c)+PL_(b,f,c)+Δ} [dB m]. The power ramping value maybe equal to a close loop power control value in a latest PUSCHtransmission before the switching. The uplink transmission power for thepreamble may be determined as the below equations,P_(PRACH,b,f,c)=min{P_(CMAX,f,c),P_(PRACH,target,f,c)+PL_(b,f,c)+f_(b,f,c) (l)} [dB m]. The source basestation (or target base station) may configure a PACH target receptionpower value P_(PRACH,target,f,c) to the wireless device. In an example,PL_(b,f,c) may be a pathloss on a downlink RS associated with the PRACHtransmission. The downlink RS may be a determined downlink RS of thelatest PUSCH transmission before the switching.

In an example, FIG. 27 illustrates an example of power control procedurefor a RACH-less handover process with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station at time T1. The one or more RRCmessages may comprise configuration parameters indicating multiple powercontrol parameter sets (PCPSs), and multiple downlink reference signals(e.g. via an RRC Reconfiguration message). The one or more RRC messagesmay comprise a counter configuration, and a counter threshold valueconfiguration (e.g. via an RRC Reconfiguration message). The wirelessdevice may receive a downlink control information indicating a NACK attime T2. The wireless device may retransmit an uplink transport block attime T3 in response to receiving the NACK. The wireless device mayincrement the counter with a step size at time T3 in response toreceiving the NACK. The wireless device may switch (or fall back) to arandom access procedure at time T4 in response the counter value beinggreater than the counter threshold value. The wireless device maycalculate (or determine), based on the a TPC command (indicated by alatest DCI before the switching), an uplink transmission power for apreamble of the target base station (or target cell) at time T5. Thewireless device may transmit, with the uplink transmission power, thepreamble on a physical random access channel (PRACH) of the target basestation (e.g., target gNB or target cell) at time T6.

In an example, FIG. 28 illustrates an example of flow chart of powercontrol process in accordance with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station. The one or more RRC messages maycomprise configuration parameters indicating multiple power controlparameter sets (PCPSs), and multiple downlink reference signals (e.g.via an RRC Reconfiguration message). The one or more RRC messages maycomprise a counter configuration, and a counter threshold valueconfiguration (e.g. via an RRC Reconfiguration message). The wirelessdevice may receive a downlink control information indicating a NACK. Thewireless device may retransmit an uplink transport block in response toreceiving the NACK. The wireless device may increment the counter with astep size in response to receiving the NACK. The wireless device mayswitch (or fall back) to a random access procedure in response thecounter value being greater than the counter threshold value. Thewireless device may calculate (or determine), based on the a TPC command(indicated by a latest DCI before the switching), an uplink transmissionpower for a preamble of the target base station (or target cell). Thewireless device may transmit, with the uplink transmission power, thepreamble on a physical random access channel (PRACH) of the target basestation (e.g., target gNB or target cell).

In an example, a wireless device may receive, from a first cell, one ormore messages comprising configuration parameters of a second cell. Theconfiguration parameters may indicate: a counter, and a counterthreshold value. The wireless device may receive, from the second cell,a downlink control information (DCI) indicating a negativeacknowledgement (NACK) in response to a transmission of an uplinktransport block to the second cell. The wireless device may incrementthe counter in response to the receiving the downlink controlinformation (DCI) indicating the negative acknowledgement (NACK). Thewireless device may switch to a random access procedure in response tothe counter value being greater than the counter threshold value. Thewireless device may calculate (or determine), based on transmit powercontrol (TPC) command indicated by the DCI, an uplink transmission powerfor a preamble of the second cell. The wireless device may transmit,with the uplink transmission power, the preamble for the random accessprocedure of the second cell. The transmission of the uplink transportblock to the second cell may comprise initial transmission orretransmission of the uplink transport block to the second cell. Thefirst cell may be a source cell or a source base station, and the secondcell may be a target cell or target base station. The calculating, basedon transmit power control (TPC) command indicated by the DCI, the uplinktransmission power may comprise taking the transmit power control (TPC)command as an input of calculating equations for the uplink transmissionpower. The incrementing the counter value may comprise increasing thecounter value with a step size.

FIG. 29 illustrates an example embodiment of uplink transport blocktransmission (or retransmission) on physical uplink shared channel(PUSCH) for a RACH-less handover process. In an example, a source basestation (e.g., source gNB or source cell) may configure multiple powercontrol parameter sets (PCPSs) for a wireless device via RRC message(s)(e.g. via an RRC Reconfiguration message). The multiple PCPSs may begenerated by a target base station (e.g., target gNB or target cell).The target gNB may transmit the multiple PCPSs information to the sourcegNB (e.g., via Xn interface). The wireless device may use the multiplePCPSs as power control parameter reference sets for determination ofuplink transmission power. The multiple PCPSs may comprise PCPS 0, PCPS1, PCPS 2, . . . , PCPS N. In an example, N may be an integer beingequal to or greater than 0. In an example, each of the multiple PCPSsmay comprise one or more power control parameters (e.g., pathlossreference signal identification, alpha set identification, and/or closedloop power control index). In an example, different PCPSs of themultiple PCPSs may comprise same values of the one or more power controlparameters. In an example, different PCPSs of the multiple PCPSs maycomprise different values of the one or more power control parameters.

The source base station (e.g., source gNB or source cell) may configuremultiple downlink reference signals for the wireless device (e.g. via anRRC Reconfiguration message). The multiple downlink reference signalsmay be downlink reference signals of the target base station (e.g.,target gNB or target cell). The target gNB may transmit the multipledownlink reference signals information to the source gNB (e.g., via Xninterface). The wireless device may use the multiple downlink referencesignals for determination of uplink transmission power for the PUSCH.The multiple downlink reference signals (RSs) may comprise RS 0, RS 1,RS 2, . . . , RS M. In an example, M may be an integer being equal to orgreater than 0. The M may be equal to the N. The multiple downlink RSsmay comprise SS\PBCH blocks (SSBs) or channel state informationreference signals (CSI-RSs). The source base station may configure anassociation relationship between the multiple downlink RSs and themultiple PCPSs to the wireless device via RRC message(s) (e.g., via theRRC Reconfiguration message). The association relationship may be a oneto one mapping relationship. In an example, an RS of the multipledownlink RSs may be associated with a PCPS of the multiple PCPSs. Thewireless device may calculate (or determine), based on power controlparameters of the PCPS, an uplink transmission power in response todetermining (or selecting) the RS based on a radio channel qualitymeasurement. The source base station may configure a counter and acounter threshold value to the wireless device via the RRC message(s)(e.g. via the RRC Reconfiguration message).

The wireless device may transmit and/or retransmit a transport blockusing multiple pre-allocated (pre-configured) uplink grants on a PUSCHof the target gNB (or target cell). The wireless device may perform atransmission (e.g., initial transmission or a retransmission) for thetransport block at time T1 (e.g., using a pre-allocated uplink grant forinitial transmission or dynamic uplink grant for retransmission). Thewireless device may reset the counter at time T1. The wireless devicemay receive a downlink control information (DCI) indicating a negativeacknowledge (NACK) at time T2. The wireless device may perform aretransmission for the transport block at time T3 with an uplink grantindicated by the DCI. The wireless device may determine (or select)different downlink beams (or different downlink RSs) as references forbeam correspondence at time T1 and T3. The wireless device may determine(or select) a same downlink beam (or a same downlink RS) as a referencefor beam correspondence at time T1 and T3. The wireless device maydetermine (or select) a downlink RS based on a radio link qualitymeasurement (e.g., reference signal received power (RSRP) or signal tointerference plus noise ratio (SINR) measurement) of the downlink RS.The wireless device may determine, based on measurements (e.g., radiolink quality measurement, such as RSRP or SINR) of the multiple downlinkRSs, a downlink RS of the multiple downlink RSs. The wireless device maydetermine (or select) the downlink RS (or a downlink beam) with a best(e.g., highest) RSRP or SINR value in the multiple downlink RSs (ormultiple downlink beams). In an example, a downlink reference signal maybe referred to as a downlink beam. The wireless device may determine aPCPS from the multiple PCPSs based on the association between the PCPSand the downlink RS. The wireless device may calculate (or determine),based on the PCPS, an uplink transmission power for the PUSCH of thetarget base station (or target cell) (e.g., not receiving a dynamicuplink grant from a base station). The wireless device may transmit,with the uplink transmission power, an uplink transport block on thePUSCH of the target base station (e.g., target gNB or target cell). Thewireless device may retransmit the uplink transport block via the PUSCHof the target base station.

In an example, a PCPS may comprise pathloss reference signalidentification q_(d), alpha set identification, and/or closed loop powercontrol index 1. The alpha set may comprise an alpha value α_(b,f,c) anda received target power value P_(O_UE_PUSCH,b,f,c). In an example,suffix indexes b, f, and c may be bandwidth part identification, carrieridentification and cell identification, respectively. The source basestation (or target base station) may configure a nominal received targetpower value P_(O_NOMINAL_PUSCH,f,c) to the wireless device. In anexample, P_(CMAX,f,c) may be a maximum power value in carrier f and cellc. In an example, Ω_(b,f,c) may be a value determined by a pre-allocateduplink grant. In an example, PL_(b,f,c)(q_(d)) may be a pathloss valueassociated with a pathloss reference signal identification q_(d). In anexample, Δ_(TF,b,f,c) may be determined by a modulation coding scheme ofthe pre-allocated uplink grant. In an example, f_(b,f,c) may be a closeloop power control parameter. In an example, f_(b,f,c) may be set to bezero in response to not receiving a dynamic uplink grant before atransmission (or retransmission). The wireless device may calculate anuplink transmission power according to the below equations based on thePCPS determined by the wireless device,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

The wireless device may determine, based on measurements of the multipledownlink RSs, a first downlink RS of the multiple downlink RSs at timeT1. The wireless device may calculate (or determine), according to aPCPS associated with the first downlink RS, a first uplink transmissionpower p1 for an uplink transport block on the PUSCH of the target basestation (e.g., not receiving a dynamic uplink grant before the firstuplink transmission). The wireless device may receive a downlink controlinformation (DCI) indicating a NACK at time T2. The DCI may comprise atransmit power control (TPC) command. The DCI may comprise an uplinkgrant. The wireless device may determine, based on measurements of themultiple downlink RSs, a second downlink RS of the multiple downlink RSsat time T3. The wireless device may calculate (or determine), accordingto a PCPS (associated with the second downlink RS) and a TPC command inthe DCI, a second uplink transmission power p2 for the uplink transportblock on the PUSCH of the target base station. The wireless device maycalculate the second uplink transmission power p2 using the belowequations,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

In an example, a wireless device may perform an initial transmission fora transport block using a pre-allocated (or pre-configured) uplinkgrant. The wireless device may receive a downlink control information(DCI) indicating a negative acknowledge (NACK). The DCI may comprise anuplink grant. The uplink grant may comprise a TPC command. The wirelessdevice may determine (or select) a downlink RS based on a radio linkquality measurement (e.g., reference signal received power (RSRP) orsignal to interference plus noise ratio (SINR) measurement) of thedownlink RS. The wireless device may determine, based on measurements(e.g., radio link quality measurement, such as RSRP or SINR) of themultiple downlink RSs, a downlink RS of the multiple downlink RSs. Thewireless device may determine (or select) the downlink RS (or a downlinkbeam) with a best (e.g., highest) RSRP or SINR value in the multipledownlink RSs (or multiple downlink beams). The wireless device maydetermine a PCPS from the multiple PCPSs according to the associationbetween the PCPS and the downlink RS. The wireless device may calculate(or determine), based on the PCPS and the TPC command indicated by theDCI, an uplink transmission power for a retransmission in response tothe NACK. The wireless device may retransmit, with the uplinktransmission power, the uplink transport block on the PUSCH of thetarget base station (e.g., target gNB or target cell). The wirelessdevice may increment the counter with a step size in response to theretransmission. The wireless device may increment the counter with astep size in response to the DCI indicating the NACK. The step size maybe equal to 1. The step size may be a configured value by a base stationvia RRC message(s). The wireless device may switch (or fall back) to arandom access procedure (e.g., comprising 2-step random access procedureor 4-step random access procedure) in response to the counter valuebeing greater than a counter threshold value. The 2-step random accessprocedure may comprise two messages comprising a first message and asecond message. The first message may comprise a preamble and an uplinktransport block (e.g., Message3 of a 4-step random access procedure).The wireless device may determine an uplink transmission power for thepreamble before transmission. The wireless device may determine anuplink transmission power for the uplink transport block beforetransmission. The wireless device may calculate (or determine) an uplinktransmission power for a preamble based on a latest DCI with a transmitpower control (TPC) command. The wireless device may calculate (ordetermine) an uplink transmission power for the preamble with a powerramping value Δ. The power ramping value Δ may be configured to thewireless device via an RRC message. The uplink transmission power forthe preamble may be determined as the below equations,P_(PRACH,b,f,c)=min{P_(CMAX,f,c), P_(PRACH,target,f,c)+PL_(b,f,c)+Δ}[dBm]. The power ramping value may be equal to a close loop powercontrol value in a latest PUSCH transmission before the switching. Theuplink transmission power for the preamble may be determined as thebelow equations, P_(PRACH,b,f,c)=min{P_(CMAX,f,c),P_(PRACH,target,f,c)+PL_(b,f,c)+f_(b,f,c)(l)} [dBm]. The source basestation (or target base station) may configure a PACH target receptionpower value P_(PRACH,target,f,c) to the wireless device. In an example,PL_(b,f,c) may be a pathloss on a downlink RS associated with the PRACHtransmission. The downlink RS may be a determined downlink RS of thelatest PUSCH transmission before the switching. The wireless device maycalculate (or determine) an uplink transmission power for Message3 ofthe 2-step random access procedure based on the latest received DCI withthe TPC command before switching to random access. The wireless devicemay calculate (or determine) an uplink transmission power for Message3in the 2-step random access procedure based on the latest received DCIand a latest determined PCPS before switching to random access. In anexample, The uplink transmission power for Message3 is written as belowequations,

$P_{{PUSCH},b,f,c} = {\min {\begin{Bmatrix}{P_{{CMAX},f,c},} \\{P_{{{O\_ {UE}}{\_ {PUSCH}}},b,f,c} + P_{{{O\_ {NOMINAL}}{\_ {PUSCH}}},f,c} + \Omega_{b,f,c} +} \\{{\alpha_{b,f,c} \cdot {{PL}_{b,f,c}\left( q_{d} \right)}} + \Delta_{{TF},b,f,c} + {f_{b,f,c}(l)}}\end{Bmatrix}\lbrack{dBm}\rbrack}}$

In an example, FIG. 30 illustrates an example of power control procedurefor a RACH-less handover process with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station at time T1. The one or more RRCmessages may comprise configuration parameters indicating multiple powercontrol parameter sets (PCPSs), and multiple downlink reference signals(e.g. via an RRC Reconfiguration message). The one or more RRC messagesmay comprise the configuration parameter indicating a counter, and acounter threshold value (e.g. via an RRC Reconfiguration message). Thewireless device may receive a downlink control information indicating aNACK at time T2. The wireless device may retransmit an uplink transportblock at time T3 in response to receiving the NACK. The wireless devicemay increment the counter with a step size at time T3 in response toreceiving the NACK. The wireless device may switch (or fall back) to arandom access procedure (e.g., comprising 2-step random access procedureor 4-step random access procedure) at time T4 in response the countervalue being greater than the counter threshold value. The wirelessdevice may calculate (or determine), based on the a TPC command(indicated by a latest DCI before the switching) and a latest determinedPCPS before the switching, an uplink transmission power for Message3 ofthe random access process at time T5. The wireless device may transmit,with the uplink transmission power, the Message 3 via a PUSCH of thetarget base station (e.g., target gNB or target cell) at time T6.

In an example, FIG. 31 illustrates an example of flow chart of powercontrol process in accordance with embodiments of the presentdisclosure. In an example, a wireless device may receive one or more RRCmessages from a source base station. The one or more RRC messages maycomprise configuration parameters indicating multiple power controlparameter sets (PCPSs), and multiple downlink reference signals (e.g.via an RRC Reconfiguration message). The one or more RRC messages maycomprise the configuration parameters indicating a counter, and acounter threshold value (e.g. via an RRC Reconfiguration message). Thewireless device may receive a downlink control information indicating aNACK. The wireless device may retransmit an uplink transport block inresponse to receiving the NACK. The wireless device may increment thecounter with a step size in response to receiving the NACK. The wirelessdevice may switch (or fall back) to a random access procedure (e.g.,comprising 2-step random access procedure or 4-step random accessprocedure) in response to the counter value being greater than thecounter threshold value. The wireless device may calculate (ordetermine), based on the a TPC command (indicated by a latest DCI beforethe switching) and a latest determined PCPS before the switching, anuplink transmission power for Message3 of the random access procedure.The wireless device may transmit, with the uplink transmission power,the Message 3 via a PUSCH of the target base station (e.g., target gNBor target cell).

In an example, a wireless device may receive, from a first cell, one ormore messages comprising configuration parameters of a second cell. Theconfiguration parameters may indicate: a counter, and a counterthreshold value. The wireless device may receive, from the second cell,a downlink control information (DCI) indicating a negativeacknowledgement (NACK) in response to a transmission of an uplinktransport block to the second cell. The wireless device may incrementthe counter in response to the receiving the downlink controlinformation (DCI) indicating the negative acknowledgement (NACK). Thewireless device may switch to a two-step random access procedure inresponse to the counter value being greater than the counter thresholdvalue. The wireless device may transmit, with an uplink transmissionpower, an uplink transport block for the two-step random accessprocedure of the second cell. The uplink transmission power may be basedon a transmission power of a latest uplink transport block transmissionbefore the switching. The transmission of the uplink transport block tothe second cell may comprise initial transmission or retransmission ofthe uplink transport block to the second cell. The first cell may be asource cell or a source base station, and the second cell may be atarget cell or target base station. The incrementing the counter valuemay comprise incrementing the counter value with a step size. Thetwo-step random access procedure may comprise a transmission of apreamble and a transmission of the uplink transport block.

According to various embodiments, a device such as, for example, awireless device, off-network wireless device, a base station, and/or thelike, may comprise one or more processors and memory. The memory maystore instructions that, when executed by the one or more processors,cause the device to perform a series of actions. Embodiments of exampleactions are illustrated in the accompanying figures and specification.Features from various embodiments may be combined to create yet furtherembodiments.

FIG. 32 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3210, a wireless device may receive RRCmessage(s) comprising configuration parameters. The RRC message(s) mayindicate a handover to a cell of a second base station. Theconfiguration parameters may indicate a plurality of power controlparameter sets (PCPSs). The configuration parameters may indicate aplurality of downlink reference signals (RSs). At 3220, the wirelessdevice may determine, based on measurements of the plurality of downlinkRSs, a downlink reference signal (RS) of the plurality of downlink RSs.At 3230, the wireless device may select a PCPS, from the plurality ofPCPSs, that is associated with the downlink RS. At 3240, the wirelessdevice may determine, based on the PCPS, an uplink transmission powerfor a physical uplink shared channel (PUSCH) of the cell. At 3250, thewireless device may transmit, with the uplink transmission power, anuplink transport block via the PUSCH of the cell.

FIG. 33 is a flow diagram as per an aspect of an example embodiment ofthe present disclosure. At 3310, a base station may transmit RRCmessage(s) comprising configuration parameters. The RRC message(s) mayindicate a handover to a cell of a second base station. Theconfiguration parameters may indicate a plurality of power controlparameter sets (PCPSs). The configuration parameters may indicate aplurality of downlink reference signals (RSs). At 3320, the base stationmay transmit the plurality of downlink reference signals (RSs).

According to various embodiments, a wireless device may receive one ormore messages indicating a handover to a cell of a second base station.The one or more messages may comprise configuration parameters of thecell. The configuration parameters may indicate a plurality of powercontrol parameter sets (PCPSs). The configuration parameters mayindicate a plurality of downlink reference signals. The wireless devicemay determine, based on measurements of the plurality of downlinkreference signals, a downlink reference signal of the plurality ofdownlink reference signals. The wireless device may select a PCPS, fromthe plurality of PCPSs, that is associated with the downlink referencesignal. The wireless device may determine, based on the PCPS, an uplinktransmission power for a physical uplink shared channel (PUSCH) of thecell. The wireless device may transmit, with the uplink transmissionpower, an uplink transport block via the PUSCH of the cell.

According to various embodiments, the wireless device may determine,based on the uplink transmission power and a ramping power value, asecond uplink transmission power for the PUSCH of the cell. According tovarious embodiments, the wireless device may retransmit, with the seconduplink transmission power, the uplink transport block via the PUSCH ofthe cell. According to various embodiments, the measurements of theplurality of downlink reference signals may comprise one or moremeasurements of a reference signal received power of the plurality ofdownlink reference signals. According to various embodiments, themeasurements of the plurality of downlink reference signals may compriseone or more measurements of a signal to interference plus noise ratio ofthe plurality of downlink reference signals. According to variousembodiments, the PCPS may comprise an identifier of a pathloss referencesignal. The PCPS may comprise an identifier of a p0 and alpha set. ThePCPS may comprise a closed loop power control index. According tovarious embodiments, radio resources of the PUSCH may be configured bythe first base station via a radio resource control (RRC)reconfiguration message. According to various embodiments, the firstbase station may comprise a source cell. The first base station maycomprise a source base station. According to various embodiments, thecell may comprise a target cell. The cell may comprise a target basestation. According to various embodiments, the determining the downlinkreference signal may comprise determining the downlink reference signalwith a best radio link quality of the plurality of downlink referencesignals.

According to various embodiments, a base station may transmit one ormore messages indicating a handover to a cell of a second base station.The one or more messages may comprise configuration parameters of thecell. The configuration parameters may indicate a plurality of powercontrol parameter sets (PCPSs). The configuration parameters mayindicate a plurality of downlink reference signals. The base station maytransmit the plurality of downlink reference signals. The base stationmay receive an uplink transport block via a physical uplink sharedchannel (PUSCH) of the cell.

According to various embodiments, a wireless device may receive, from afirst base station, one or more messages indicating a handover to a cellof a second base station. The one or more messages may compriseconfiguration parameters of the cell. The configuration parameters mayindicate a plurality of power control parameter sets (PCPSs). Theconfiguration parameters may indicate a plurality of downlink referencesignals. The wireless device may transmit a first transport block viathe cell. The wireless device may receive, from the cell, a downlinkcontrol information (DCI) indicating a negative acknowledgement (NACK)for the first transport block. The wireless device may determine, basedon measurements of the plurality of downlink reference signals, adownlink reference signal of the plurality of downlink referencesignals. The wireless device may select a PCPS, from the plurality ofPCPSs, that is associated with the downlink reference signal. Thewireless device may determine, based on the PCPS and a transmit powercontrol (TPC) command indicated by the DCI, an uplink transmission powerfor a physical uplink shared channel (PUSCH) of the cell. The wirelessdevice may transmit, with the uplink transmission power, a second uplinktransport block via the PUSCH of the cell.

According to various embodiments, a first base station may transmit, toa wireless device, one or more messages indicating a handover to a cellof a second base station. The one or more messages may compriseconfiguration parameters of the cell. The configuration parameters mayindicate a plurality of power control parameter sets (PCPSs). Theconfiguration parameters may indicate a plurality of downlink referencesignals. The first base station may receive a first transport block viathe cell. The first base station may transmit a downlink controlinformation (DCI) indicating a negative acknowledgement (NACK) for thefirst transport block. The first base station may receive a seconduplink transport block a physical uplink shared channel (PUSCH) of thecell.

According to various embodiments, a wireless device may receive, from afirst base station, one or more messages indicating a handover to a cellof a second base station. The one or more messages may compriseconfiguration parameters. The configuration parameters may indicate acounter threshold value of a counter for unsuccessful transmissions of atransport block via the cell. The wireless device may transmit a firsttransport block via the cell. The wireless device may receive, from thecell, a downlink control information (DCI) indicating a negativeacknowledgement (NACK) for the first transport block. The wirelessdevice may increment the counter in response to the receiving the DCIindicating the NACK. The wireless device may switch to a random accessprocedure for the cell in response to the counter value exceeding thecounter threshold value. The wireless device may transmit, via the cell,a preamble for the random access procedure.

According to various embodiments, a first base station may transmit, toa wireless device, one or more messages indicating a handover to a cellof a second base station. The one or more messages may compriseconfiguration parameters. The configuration parameters may indicate acounter threshold value of a counter for unsuccessful transmissions of atransport block via the cell. The first base station may receive a firsttransport block via the cell. The first base station may transmit adownlink control information (DCI) indicating a negative acknowledgement(NACK) for the first transport block. The first base station mayreceive, via the cell, a preamble for a random access procedure.

According to various embodiments, a wireless device may receive, from afirst base station, one or more messages indicating a handover to a cellof a second base station. The one or more messages may compriseconfiguration parameters. The configuration parameters may indicate acounter threshold value of a counter for unsuccessful transmissions of atransport block via the cell. The wireless device may transmit a firsttransport block via the cell. The wireless device may receive, from thecell, a downlink control information (DCI) indicating a negativeacknowledgement (NACK) for the first transport block. The wirelessdevice may increment the counter in response to the receiving the DCIindicating the NACK. The wireless device may switch to a two-step randomaccess procedure for the cell in response to the counter value exceedingthe counter threshold value. The wireless device may transmit, with anuplink transmission power via the cell, a second uplink transport blockfor the two-step random access procedure. The uplink transmission powermay be determined based on a latest transmission power of the firstuplink transport block before the switching.

According to various embodiments, a first base station may transmit, toa wireless device, one or more messages indicating a handover to a cellof a second base station. The one or more messages may compriseconfiguration parameters. The configuration parameters may indicate acounter threshold value of a counter for unsuccessful transmissions of atransport block via the cell. The first base station may receive a firsttransport block via the cell. The first base station may transmit adownlink control information (DCI) indicating a negative acknowledgement(NACK) for the first transport block. The first base station mayreceive, via the cell, a second uplink transport block for a two-steprandom access procedure.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. When thisdisclosure refers to a base station communicating with a plurality ofwireless devices, this disclosure may refer to a subset of the totalwireless devices in a coverage area. This disclosure may refer to, forexample, a plurality of wireless devices of a given LTE or 5G releasewith a given capability and in a given sector of the base station. Theplurality of wireless devices in this disclosure may refer to a selectedplurality of wireless devices, and/or a subset of total wireless devicesin a coverage area which perform according to disclosed methods, and/orthe like. There may be a plurality of base stations or a plurality ofwireless devices in a coverage area that may not comply with thedisclosed methods, for example, because those wireless devices or basestations perform based on older releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed to one or more of the various embodiments.

If A and B are sets and every element of A is also an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayalso refer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, various embodiments are disclosed. Limitations,features, and/or elements from the disclosed example embodiments may becombined to create further embodiments within the scope of thedisclosure.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Furthermore, many features presented above are described as beingoptional through the use of “may” or the use of parentheses. For thesake of brevity and legibility, the present disclosure does notexplicitly recite each and every permutation that may be obtained bychoosing from the set of optional features. However, the presentdisclosure is to be interpreted as explicitly disclosing all suchpermutations. For example, a system described as having three optionalfeatures may be embodied in seven different ways, namely with just oneof the three possible features, with any two of the three possiblefeatures or with all three of the three possible features.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (i.e.hardware with a biological element) or a combination thereof, all ofwhich may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or LabVIEWMathScript.Additionally, it may be possible to implement modules using physicalhardware that incorporates discrete or programmable analog, digitaland/or quantum hardware. Examples of programmable hardware comprise:computers, microcontrollers, microprocessors, application-specificintegrated circuits (ASICs); field programmable gate arrays (FPGAs); andcomplex programmable logic devices (CPLDs). Computers, microcontrollersand microprocessors are programmed using languages such as assembly, C,C++ or the like. FPGAs, ASICs and CPLDs are often programmed usinghardware description languages (HDL) such as VHSIC hardware descriptionlanguage (VHDL) or Verilog that configure connections between internalhardware modules with lesser functionality on a programmable device. Theabove mentioned technologies are often used in combination to achievethe result of a functional module.

The disclosure of this patent document incorporates material which issubject to copyright protection. The copyright owner has no objection tothe facsimile reproduction by anyone of the patent document or thepatent disclosure, as it appears in the Patent and Trademark Officepatent file or records, for the limited purposes required by law, butotherwise reserves all copyright rights whatsoever.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example, and notlimitation. It will be apparent to persons skilled in the relevantart(s) that various changes in form and detail can be made thereinwithout departing from the scope. In fact, after reading the abovedescription, it will be apparent to one skilled in the relevant art(s)how to implement alternative embodiments. Thus, the present embodimentsshould not be limited by any of the above described exemplaryembodiments.

In addition, it should be understood that any figures which highlightthe functionality and advantages, are presented for example purposesonly. The disclosed architecture is sufficiently flexible andconfigurable, such that it may be utilized in ways other than thatshown. For example, the actions listed in any flowchart may bere-ordered or only optionally used in some embodiments.

Further, the purpose of the Abstract of the Disclosure is to enable theU.S. Patent and Trademark Office and the public generally, andespecially the scientists, engineers and practitioners in the art whoare not familiar with patent or legal terms or phraseology, to determinequickly from a cursory inspection the nature and essence of thetechnical disclosure of the application. The Abstract of the Disclosureis not intended to be limiting as to the scope in any way.

Finally, it is the applicant's intent that only claims that include theexpress language “means for” or “step for” be interpreted under 35U.S.C. 112. Claims that do not expressly include the phrase “means for”or “step for” are not to be interpreted under 35 U.S.C. 112.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice from a first base station, one or more messages indicating ahandover to a cell of a second base station, the one or more messagescomprising configuration parameters of the cell, wherein theconfiguration parameters indicate: a plurality of power controlparameter sets (PCPSs); and a plurality of downlink reference signals;determining, based on measurements of the plurality of downlinkreference signals, a downlink reference signal of the plurality ofdownlink reference signals; selecting a PCPS, from the plurality ofPCPSs, that is associated with the downlink reference signal;determining, based on the PCPS, an uplink transmission power for aphysical uplink shared channel (PUSCH) of the cell; and transmitting,with the uplink transmission power, an uplink transport block via thePUSCH of the cell.
 2. The method of claim 1, further comprisingdetermining, based on the uplink transmission power and a ramping powervalue, a second uplink transmission power for the PUSCH of the cell. 3.The method of claim 2, further comprising retransmitting, with thesecond uplink transmission power, the uplink transport block via thePUSCH of the cell.
 4. The method of claim 1, wherein the measurements ofthe plurality of downlink reference signals comprise one or moremeasurements of a reference signal received power of the plurality ofdownlink reference signals.
 5. The method of claim 1, wherein themeasurements of the plurality of downlink reference signals comprise oneor more measurements of a signal to interference plus noise ratio of theplurality of downlink reference signals.
 6. The method of claim 1,wherein the PCPS comprises at least one of: an identifier of a pathlossreference signal; an identifier of a p0 and alpha set; and a closed looppower control index.
 7. The method of claim 1, wherein radio resourcesof the PUSCH are configured by the first base station via a radioresource control reconfiguration message.
 8. The method of claim 1,wherein the first base station comprises: a source cell; or a sourcebase station.
 9. The method of claim 1, wherein the cell comprises atarget cell or a target base station.
 10. The method of claim 1, whereinthe determining the downlink reference signal comprises determining thedownlink reference signal with a best radio link quality of theplurality of downlink reference signals.
 11. A wireless devicecomprising: one or more processors; memory storing instructions that,when executed by the one or more processors, cause the wireless deviceto: receive, from a first base station, one or more messages indicatinga handover to a cell of a second base station, the one or more messagescomprising configuration parameters of the cell, wherein theconfiguration parameters indicate: a plurality of power controlparameter sets (PCPSs); and a plurality of downlink reference signals;determine, based on measurements of the plurality of downlink referencesignals, a downlink reference signal of the plurality of downlinkreference signals; select a PCPS, from the plurality of PCPSs, that isassociated with the downlink reference signal; determine, based on thePCPS, an uplink transmission power for a physical uplink shared channel(PUSCH) of the cell; and transmit, with the uplink transmission power,an uplink transport block via the PUSCH of the cell.
 12. The wirelessdevice of claim 11, wherein the instructions, when executed by the oneor more processors, further cause the wireless device to determine,based on the uplink transmission power and a ramping power value, asecond uplink transmission power for the PUSCH of the cell.
 13. Thewireless device of claim 12, wherein the instructions, when executed bythe one or more processors, further cause the wireless device toretransmit, with the second uplink transmission power, the uplinktransport block via the PUSCH of the cell.
 14. The wireless device ofclaim 11, wherein the measurements of the plurality of downlinkreference signals comprise one or more measurements of a referencesignal received power of the plurality of downlink reference signals.15. The wireless device of claim 11, wherein the PCPS comprises at leastone of: an identifier of a pathloss reference signal; an identifier of ap0 and alpha set; and a closed loop power control index.
 16. Thewireless device of claim 11, wherein radio resources of the PUSCH areconfigured by the first base station via a radio resource controlreconfiguration message.
 17. The wireless device of claim 11, whereinthe first base station comprises: a source cell; or a source basestation.
 18. The wireless device of claim 11, wherein the cellcomprises: a target cell; or a target base station.
 19. The wirelessdevice of claim 11, wherein the instructions, when executed by the oneor more processors, further cause the wireless device to determine thedownlink reference signal with a best radio link quality of theplurality of downlink reference signals.
 20. A system comprising: a basestation comprising: one or more second processors; memory storing secondinstructions that, when executed by the one or more second processors,cause the base station to: transmit one or more messages indicating ahandover to a cell of a second base station, the one or more messagescomprising configuration parameters of the cell, wherein theconfiguration parameters indicate: a plurality of power controlparameter sets (PCPSs); and a plurality of downlink reference signals;transmit the plurality of downlink reference signals; and a wirelessdevice comprising: one or more processors; memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: receive the one or more messages; determine, based onmeasurements of the plurality of downlink reference signals, a downlinkreference signal of the plurality of downlink reference signals; selecta PCPS, from the plurality of PCPSs, that is associated with thedownlink reference signal; determine, based on the PCPS, an uplinktransmission power for a physical uplink shared channel (PUSCH) of thecell; and transmit, with the uplink transmission power, an uplinktransport block via the PUSCH of the cell.